feat: add branch snapshot deploy workflow - #165
Draft
TaurMorchant wants to merge 1 commit into
Draft
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
2 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.
Why. Deploying a feature branch republishes
X.Y.Z-SNAPSHOTand overwrites whatmainor another branchpublished under that version.
What. The caller for the branch-snapshot deploy: publishes the branch as
X.Y.Z-<branch>-SNAPSHOT, tests skippedby default. Mechanism and documentation: Netcracker/qubership-core-infra#237.
Requires inter-module dependencies on SNAPSHOT versions (Netcracker/qubership-core-bulk-release#67), and
-SNAPSHOTonly on internal artifacts.Before merging. infra#237 lands first, then the
uses:ref moves from@feat/consistent-snapshotsto a SHA pin.infra#237 also has to accept
MAVEN_TOKEN— it hardcodesgithub.token, which cannot publish to this monorepo'sper-module registries.