-
Notifications
You must be signed in to change notification settings - Fork 109
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
Angular Service Build Failed because of Jenkins Hardware Limits #834
Comments
@suryajak @deepusundar Please have a look. |
@francis-ve Thanks for reporting the issue. Please find the Limitations section in Jazz-Installer https://github.com/tmobile/jazz-installer/wiki#limitations As suggested, we are already working on decreasing the threshold limits. Also can increase the CPU limit based on the requirement https://github.com/tmobile/jazz-installer/blob/668020d3e44b0d128b5ceaedc1eaa51e1e14ce70/installscripts/jazz-terraform-unix-noinstances/variables.tf#L128. At this time, we are not clearing any work space related files for the core services through code. But can manually delete those files/folders through Jenkins script console. |
@rajeevr2715 Thank you for the information you shared. |
Description
We are adding angular service deployment support to Jazz Platform. For this process, Jazz platform have to take angular build to generate html,css & js files & deploy it to cloud. But before that Jazz have to install/update library packages from node package manager(NPM). This
npm install
ornpm update
requires sufficient cpu units and memory to properly build cache and pull packages and install it to the service. This is getting failed sometimes because of the Jenkins container hardware limits.Observations
website buildpack failed
. Reason:npm ERR! nospc ENOSPC: no space left on device
CPUUtilization
of the serviceecs_cluster_jenkins
hits 100% during npm process.Suggestions
Task CPU
which is part of the Jenkins Task Definition (ecs_task_definition_jenkins
).disk free space threshold
&temp free space threshold
in theJenkins master node
configuration.The text was updated successfully, but these errors were encountered: