Add scheduled builds - #294
Merged
Merged
Conversation
Refactor build workflows to allow reuse through workflow calls, and to make it easier to define different behaviour for different triggers. Signed-off-by: Mark S. Lewis <mark_lewis@uk.ibm.com>
bestbeforetoday
force-pushed
the
schedule
branch
from
February 9, 2023 18:14
c7a65a7 to
c3b1f02
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
bestbeforetoday
marked this pull request as ready for review
February 9, 2023 18:30
mbwhite
approved these changes
Feb 21, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refactor build workflows to allow reuse through workflow calls, and to make it easier to define different behaviour for different triggers.
This refactor means the branch protection checks before PRs can be merged needs to be updated to only require Pull request success.
Note: The publishing and possibly some of the other workflows look to be more up-to-date in the release-2.5 branch than in the main branch. This change aims to retain the same behaviour as the main branch that it updates, not to incorporate any improvements made to the publishing in the release-2.5 branch.