-
Notifications
You must be signed in to change notification settings - Fork 327
ci: use k8s pod template agents #2311
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
Conversation
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
|
1515460 to
e17e1d3
Compare
| - sleep | ||
| args: | ||
| - infinity | ||
| ## TODO: Faster builds with some cached artifacts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
@Mergifyio refresh |
✅ Pull request refreshed |
| */ | ||
| stage('Smoke Tests 01') { | ||
| agent { label 'linux && immutable' } | ||
| agent { kubernetes { yamlFile '.ci/k8s/OpenJdkPod.yml' } } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC, this was the way to ensure the parallel stages don't clash with the workspace when using the top-level k8s definition.
I need to clarify this to be sure this is the right pattern to be used.
|
@Mergifyio update |
✅ Branch has been successfully updated |
|
@v1v do we want to proceed with this, or can I close this PR? |
|
Closing this issue as we are moving away from Jenkins |


What does this PR do?
PoC with K8s CI Workers
Checklist
[ ] This is an enhancement of existing features, or a new feature in existing plugins[ ] This is a bugfix[ ] This is a new pluginWhy
For instance, the agent is provisioned almost immediately, compared to the 2 minutes average per CI worker
Actions