Improve master -> quarkus-master branch scheduled synchronization workflow #1127
Conversation
This file contains 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
oscerd
approved these changes
Apr 23, 2020
lburgazzoli
approved these changes
Apr 23, 2020
jamesnetherton
force-pushed
the
improve-quarkus-master-sync
branch
from
55394cb
to
f69dd36
Compare
jamesnetherton
force-pushed
the
improve-quarkus-master-sync
branch
from
f69dd36
to
245a4a6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some changes to improve the process of syncing the latest work on the master branch to the quarkus-master branch. There's a few things I'd like to improve, but I think this is a decent starting point.
Some things to be aware of:
I externalized the native integration test categories so they can be shared across workflow files in
.github/test-categories.yaml.Added build status reporting functionality to the sync job. It'll automatically create an issue for investigating failures and will auto close it when the build is successful.
The cache action does not support the schedule event 🙃. So instead I use the artifact action to upload / download the m2 repository between jobs. This actually turns out to be more reliable than the cache anyway. To avoid exceeding quotas I added another workflow to periodically clean up the generated artifacts.
If this works well, I'll look at applying the same thing for the master -> camel-master branch sync.