elliottt opened PR #5286 from trevor/skip-release-builds-on-branches
to main
:
Disable the
Build
jobs on branches, but leave it for main and version tag builds.
<!--Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
elliottt edited PR #5286 from trevor/skip-release-builds-on-branches
to main
:
Disable the
Build
jobs on branches, but leave it for main and version tag builds. We'll need to remove theBuild
jobs as requirements for merging for this PR to be mergable.
<!--Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
elliottt edited PR #5286 from trevor/skip-release-builds-on-branches
to main
:
Disable the
Build
jobs on branches, but leave it for main and version tag builds. We'll need to remove theBuild
jobs as requirements for merging for this PR to be mergable. This won't substantially reduce build time, but it will reduce the number of parallel jobs spawned, which should free up some capacity organization-wide.
<!--Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
elliottt has marked PR #5286 as ready for review.
elliottt requested alexcrichton for a review on PR #5286.
elliottt submitted PR review.
elliottt created PR review comment:
I'm undecided about leaving this guard in. It seems nice to avoid accidentally triggering this in the future, but it's also redundant with the new
if
at the job level.
alexcrichton submitted PR review.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
jameysharp created PR review comment:
How about using this pattern?
startsWith(github.ref, 'refs/heads/release-')
jameysharp submitted PR review.
elliottt submitted PR review.
elliottt created PR review comment:
That works for me!
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt submitted PR review.
elliottt created PR review comment:
I'll add a note about keeping it because we run these jobs on
release-*
branches.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
alexcrichton submitted PR review.
alexcrichton submitted PR review.
alexcrichton created PR review comment:
I think that this may not actually fire for
release-*
branches since we already only run forpush
events on themain
branch only (plus tags). Could this be inverted as "run if not PR or if release branch?"
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt submitted PR review.
elliottt created PR review comment:
I had totally forgotten about the top-level
on
predicate, thanks for catching this!
alexcrichton submitted PR review.
alexcrichton created PR review comment:
Could this have a
pull_request:
added therelease-*
branches as well? Additionally it should be ok to removerelease-*
from thebranches:
to avoid the double builds for PRs and release branches on merge.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
alexcrichton submitted PR review.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt updated PR #5286 from trevor/skip-release-builds-on-branches
to main
.
elliottt edited PR #5286 from trevor/skip-release-builds-on-branches
to main
:
Disable the
Build
jobs on branches, but leave it for main, version tag, andrelease-*
builds. We'll need to remove theBuild
jobs as requirements for merging for this PR to be mergable. This won't substantially reduce build time, but it will reduce the number of parallel jobs spawned, which should free up some capacity organization-wide.
<!--Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
elliottt merged PR #5286.
Last updated: Nov 22 2024 at 16:03 UTC