This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Adding two pipelines for release branch for ci/cd (release 22.0.x) #841
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Change Description
Adjusting the workflows to add two new pipelines to build and test with the release branches. Also changed the existing files to rename them to develop. Adjusted the dockerfile to take build arguments specifying which branches to use for eos and cdt. Lastly, changed the release stable, prerelease, and edge release workflows to have similar code.
CI pipeline uses release_22.0.x docker tag for this branch specifically
API Changes
Documentation Additions