-
Notifications
You must be signed in to change notification settings - Fork 42
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errorsExpand to view the tests failures> Show only the first 10 test failures
|
.ci/build-docker-images.groovy
Outdated
@@ -25,7 +25,7 @@ pipeline { | |||
quietPeriod(10) | |||
} | |||
triggers { | |||
cron 'H H(0-5) * * 1-5' | |||
cron '@daily' |
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.
do not use daily, it will run on weekends, and 24h after the last execution so the time is not fixed.
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.
Ok, I used what we added in the apm-pipeline-library for building images: https://github.com/elastic/apm-pipeline-library/blob/master/.ci/jobs/beats-docker-images-pipeline.yml#L27
What is the recommended cron trigger? Maybe weekly/monthly is enough
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.
'H H(0-5) * * 1-5' Monday to Friday anytime between 00:00 AM to 05:00 AM this is fine, the key is to set a range (H(0-5)) of hours where the build can run, Jenkins will manage to not overload the instance in that range.
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.
Ok, this is what we use for the nightly scheduled pipelines. Will use what we have in there
triggers { | ||
cron 'H H(0-5) * * 1-5' | ||
cron 'H H(4-5) * * 1-5' |
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.
Use same cron than in the nightly builds
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.
NIT: normalise the names
Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
Done 😊 I used lowercase for params and uppercase for env vars on purpose, as I thought there was a naming convention. If it's not there, we can add it to the shared library docs. |
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Log outputExpand to view the last 100 lines of log output
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
* master: Support fleet-server-service-token (elastic#1096) fix: use wider selector for ARM workers (elastic#1103) feat: bootstrap fleet-server for the deployment of regular elastic-agents (elastic#1078) fix: use proper variable name (elastic#1102) fix: branch_specifier is needed (elastic#1097) Move kubernetes/kubectl/kind code to internal project layout (elastic#1092) fix: update JJBB with proper values (elastic#1093) feat: support building centos/debian Docker images in multiplatform format (elastic#1091) Kubernetes autodiscover suite (elastic#1064)
What does this PR do?
It reverts dddba26, as the branch_specifier is required, although failing the first time the build is executed (params are not there).
We are changing the schedued trigger to daily
Why is it important?
Checklist
make notice
in the proper directory)Author's Checklist
Related issues