-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Optimize build_instrumented job
#6954
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
Changes from 1 commit
c379ee9
7c988d1
828f5ee
c06dbf1
a001917
107eacf
3ef66a4
1377083
f3d1741
afe01ee
28ea21e
143de12
9c193f0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -339,7 +339,24 @@ workflows: | |
| version: 2 | ||
| commit: | ||
| jobs: | ||
| - compile | ||
| - hold_pr: | ||
| type: approval | ||
| filters: | ||
| branches: | ||
| ignore: | ||
| - master | ||
| - compile: | ||
| filters: | ||
| branches: | ||
| only: | ||
| - master | ||
| - compile: | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it possible to have two jobs with the same name (
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. They both reference the |
||
| requires: | ||
| - hold_pr | ||
| filters: | ||
| branches: | ||
| ignore: | ||
| - master | ||
| - check_quality: | ||
| requires: | ||
| - compile | ||
|
|
||
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.
I often find that I might be committing/pushing quickly and that context, CI will be constantly starting and cancelling workflow runs. Add a manual approval step means we only end up running jobs when we actually care about the result. I'd like to try this, but definitely let me know if you feel like it's getting annoying @grzesiek2010.
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.
I agree with your rationale, but isn’t it possible to differentiate between draft and ready-for-review PRs and trigger jobs only for those that are ready for review?
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.
Good idea! It looks like this might be possible with the new Github triggers, but I'm not sure that we'd be able to have it always run for non-drafts and optionally for drafts (you still probably want CI on request for drafts). We could always just use the GitHub API (probably through
gh).I think that's probably a future improvement though: I think we either go with the basic version as-is or remove the
hold_prcheck for now.