Conversation
To be added in elastic#13484
Daily step is going to be added as part of elastic#13484
💛 Build succeeded, but was flaky
Failed CI StepsHistorycc @mrodm |
🚀 Benchmarks reportTo see the full report comment with |
|
jsoriano
left a comment
jsoriano
left a comment
There was a problem hiding this comment.
LGTM. Selecting steps through environment variables looks a bit fragile, but seems easy to redistribute the steps executed on each schedule.
| if: | | ||
| build.env('TEST_PACKAGES_7_BRANCH') == "true" |
There was a problem hiding this comment.
Would it make sense to have multiple pipelines instead of these conditions?
There was a problem hiding this comment.
I thought that it could be easier to just manage one buildkite pipeline with all the steps and select the steps required in each build using environment variables. That would avoid creating several new Buildkite jobs.
It could be tested like this, if there are any issues we could create new Buildkite pipelines later.
| env: | ||
| TEST_PACKAGES_7_BRANCH: "true" | ||
| TEST_PACKAGES_SERVERLESS: "true" | ||
| REPUBLISH_PACKAGES: "true" |
There was a problem hiding this comment.
Well, allowing to select steps this way also looks good.
3 participants
Proposed commit message
This PR adds more schedules to the daily CI job. This will help to split the load in different builds.
Example of build testing packages with 7.x stack:
https://buildkite.com/elastic/integrations-schedule-daily/builds/539
Author's Checklist
Related issues