awslabs / awslabs/aws-codebuild-jenkins-plugin
infinite codebuild provisioning on unsuccessful container provisioning.
- Dominant language
- Java
- Stars
- 156
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
Hi There
I am using aws codebuild to spin up new slave nodes. I have configured it into Jenkins cloud with label.
When I run a pipeline with a label and if codebuild fails to provision then it keeps on asking aws codebuild to provision a codebuild which increases the cost of AWS codebuild service.
I want to implement the feature that if it fails to provision codebuild after 5 retries then job should fail with error.
Can I work on this feature.
Please help me to implement this feature.
Contributor guide
Research direction
Start by tracing the plugin's AWS CodeBuild provisioning and retry behavior, then inspect how Jenkins reports a failed provisioning attempt to the job. Done means provisioning stops after five unsuccessful retries and the pipeline receives an error instead of triggering more CodeBuild requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100