-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
chore(ci): Reduce the number of jobs, move some of them to once a day #19001
Conversation
CodSpeed Performance ReportMerging #19001 Summary
Benchmarks breakdown
|
7d55b91
to
f08ce4c
Compare
1bfbe8d
to
32982b9
Compare
Since new workflows won't be visible until we merge this to main, I'd suggest we do a review now and then test it later. |
Following builds will be done once a day after this is merged: - all binary engine tests - json protocol with non-minimal supported version If PR contains `ci build all` comment, all of those things will be checked. If not, the job that will test them will run at 9am UTC. Since we now need two jobs on different schedules, we need a way to differentiate them: for that reason, both buildpulse and new nightly jobs are implemented as separate workflows, that call original one passing the reason (daily/buildpulse) as a parameter.
Co-authored-by: Joël Galeran <Jolg42@users.noreply.github.com>
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.
Thanks a lot ✨
Following builds will be done once a day after this is merged:
If PR contains
ci test all
comment, all of those things will bechecked. If not, the job that will test them will run at 4am UTC from Monday to Friday.
Since we now need two jobs on different schedules, we need a way to
differentiate them: for that reason, both buildpulse and new nightly
jobs are implemented as separate workflows, that call original one
passing the reason (daily/buildpulse) as a parameter.