-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure build RAM capacity #759
Comments
Daily summary 11/13: Changes have been implemented and merged. Just needed to change hyperctl-image to take in CPU and memory arguments and to pass in that data in the executor-k8s-vm. Currently working on verifying the changes. |
Pulls in hyperctl image and executor-k8s-vm changes screwdriver-cd/hyperctl-image#11 screwdriver-cd/executor-k8s-vm#14 Original issues: screwdriver-cd/screwdriver#758, screwdriver-cd/screwdriver#759
Daily summary 11/14: Tested out the new hyperctl image changes by running a build using the executor
The CPU and memory were set to the "HIGH" settings, 6 vcpu and 12288 MB, respectively. The initial work is considered done. Changes might be made in the future to tweak those values so they better suit our users' needs. |
Context
As a pipeline owner, I want the ability to configure my build to be run on a machine with higher RAM than what is allocated by default.
Objective
RAM allocated by default might not be suitable for user build jobs with higher memory constraints. Users should be allowed to specify larger RAM for their builds.
Requirements
screwdriver.yaml
user's RAM requirement.The text was updated successfully, but these errors were encountered: