Repository navigation
Build and publish versions with the shared version tool - #9
Merged
Merged
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
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.
Summary
A release branch or a Renovate branch of data-transform-api builds the plain
version that only
mastershould, such as1.5.0, and Gradle publishes it toplatform, the releases repository. A feature branch publishes there too. Thepublished version also loses every digit of a branch's name, so
feature/GH-60-fixpublishes as1.5.0-GH--FIX, and branches that differ onlyin their issue number publish the same version.
This adopts the shared version tool, the one set of version rules for every
Cinchapi repo, from cinchapi/cinchapi-agent-skills#70. Part of
cinchapi/cinchapi-agent-skills#67.
Behavior
version.shis a copy of the shared tool at the pinned commit of.agents, andevery skills pull refreshes it. Gradle and
tools/releasecall it as before.master1.5.0platformrelease/*1.5.0-rc<n>platform-snapshotsdevelop1.5.0-SNAPSHOTplatform-snapshotsfeature/GH-60-fix1.5.0-FEATURE-GH-60-FIXplatform-snapshotsOnly a plain X.Y.Z goes to the releases repository. A release candidate carries
its build number as
-rc<n>, so each candidate is a distinct version.version.sh X.Y.Zsets.versionand changes no other file, since nothing elsein the repo names its version.