[
https://issues.apache.org/jira/browse/GEODE-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104671#comment-17104671
]
ASF subversion and git services commented on GEODE-8016:
--------------------------------------------------------
Commit 96e6250652d1f387314965d80e42f4fc2b20ede5 in geode's branch
refs/heads/support/1.12 from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=96e6250 ]
GEODE-8016: publish with non-zero-padded build ids instead of SNAPSHOT. (#5090)
* Artifacts take the form `1.12.1-build.123` instead of `1.12.1-SNAPSHOT`.
* checkPom task has been modified to use a slug instead of an always
changing version.
* Gradle clients will use the greedy "1.12.1-build+" notation
* Maven clients will use semver v1.0 "[1.12.1-build,1.13.0)" notation.
Signed-off-by: Sean Goller <sgol...@pivotal.io>
(cherry picked from commit a4c8b9ed8bbea584f798164fa5308d236e9b6048)
(cherry picked from commit 39c522e340196cb30d55d81d93c63028938cd782)
> Replace Maven SNAPSHOT with enumerated build-id artifacts
> ---------------------------------------------------------
>
> Key: GEODE-8016
> URL: https://issues.apache.org/jira/browse/GEODE-8016
> Project: Geode
> Issue Type: Task
> Components: build, ci
> Reporter: Robert Houghton
> Assignee: Robert Houghton
> Priority: Major
>
> To better support repeatable builds in CI, publish artifacts in the form
> `1.2.3-build.123` instead of `1.2.3-SNAPSHOT` with the SNAPSHOT dynamically
> changing. As an example, the `geode-examples` pipeline would be able to grab
> a distinct artifact for build-and-test, instead of an unrepeatable, invisibly
> rolling `SNAPSHOT`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
