[1.29] migrate from Drone to GitHub Actions #355
Merged
Conversation
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
HarrisonWAffel
approved these changes
May 1, 2024
kinarashah
approved these changes
May 2, 2024
This was referenced May 10, 2024
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.
This PR migrates the current Drone CI to the GitHub Actions and matches the existing behavior as closely as possible.
To test the workflow
Release, a modified version of the code which uses my own Docker credentials is used to cut the tag v1.29.3-jq5. The workflowReleaseruns successfully (here) and pushes the image to Dockerhub (here).As we are maintaining multiple branches, backport PRs will be made after the initial one is merged and validated.
SURE-8209