feat: [CI-21851]: Adding upload to GCS step - #12
Open
tapankarangiya wants to merge 1 commit into
Open
tapankarangiya wants to merge 1 commit into
tapankarangiya wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 pull request adds a new deployment step to the pipeline configuration. The main change is the introduction of a step to upload binaries to Google Cloud Storage (GCS) when a build is triggered by a tag.
Deployment pipeline enhancement:
Upload_Binaries_To_GCSstep to.harness/harness.yamlthat uses theUpload_Binary_GCS_TItemplate to upload binaries from/harness/releaseto a GCS bucket underdrone-artifactory/<+trigger.tag>/, only when the build type is a tag.