This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Centralize EOSIO Pipeline #7412
Closed
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
I have migrated the EOSIO Buildkite pipeline from this repo to the central pipeline repo in
auto-buildkite-pipelinespull request 110. However, themasterbranch still has the.pipelinebranchfile pointing tolegacy-osso, because that file acts blindly on all pipelines, the eosio pipeline is broken on master. This pull request resolves this issue.See Also
auto-buildkite-pipelineseos:release/1.6.xeos:release/1.7.xeos:release/1.8.xeos:developConsensus Changes
None.
API Changes
None.
Documentation Additions
None.