chore(build): trigger downstream repo release#1657
Merged
mynktl merged 2 commits intoopenebs-archive:masterfrom Apr 8, 2020
kmova:tag-downstream
Merged
chore(build): trigger downstream repo release#1657mynktl merged 2 commits intoopenebs-archive:masterfrom kmova:tag-downstream
mynktl merged 2 commits intoopenebs-archive:masterfrom
kmova:tag-downstream
Conversation
OpenEBS Control Plane code is split across multiple repos. For releasing control plane code, multiple repo's need to be tagged in a certain order. This fix will help to trigger the release on the downstream repo. In this case, after releasing openebs/maya, the following repos should be tagged: - openebs/velero-plugin - openebs/cstor-csi - openebs/jiva-operator Note: Due to multiple jobs running in travis, the release on the downstream should be done only after the longest job that pushes the containers is completed. This is manually configured via ENV variable RELEASE_DOWNSTREAM. Signed-off-by: kmova <kiran.mova@mayadata.io>
kmova
requested review from
mynktl,
prateekpandey14,
shubham14bajpai and
utkarshmani1997
In case of travis, the $TRAVIS_BRANCH contains the same value as $TRAVIS_TAG. Example: 1.9.0-RC1 tag and 1.9.0-RC1 branch. Due to this the git-release script failed. This commit adds a step to convert the TRAVIS_TAG to corresponding release branch. Example: 1.9.0-RC1 should happen from v1.9.x Note: OpenEBS release follow the SemVer release format of major.minor.patch[-build-meta] Signed-off-by: kmova <kiran.mova@mayadata.io>
mynktl
reviewed
Apr 8, 2020
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
6 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.
OpenEBS Control Plane code is split across multiple repos.
For releasing control plane code, multiple repo's need
to be tagged in a certain order.
This fix will help to trigger the release
on the downstream repo. In this case, after
releasing openebs/maya, the following repos should be
tagged:
Note: Due to multiple jobs running in travis,
the release on the downstream should be done
only after the longest job that pushes the
containers is completed. This is manually
configured via ENV variable RELEASE_DOWNSTREAM.
Signed-off-by: kmova kiran.mova@mayadata.io
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Checklist:
documentationtagbreaking-changestagrequires-upgradetag