[
https://issues.apache.org/jira/browse/GEODE-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780837#comment-16780837
]
ASF subversion and git services commented on GEODE-6460:
--------------------------------------------------------
Commit d37836c234723cadcaea52b738db940804c1d668 in geode's branch
refs/heads/develop from Patrick Rhomberg
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d37836c ]
GEODE-6460: Add semver controls to pipeline. (#3250)
* These are only visible under the 'Semver Management' group.
> geode-build-version does not automatically update with a new version
> --------------------------------------------------------------------
>
> Key: GEODE-6460
> URL: https://issues.apache.org/jira/browse/GEODE-6460
> Project: Geode
> Issue Type: Improvement
> Reporter: Patrick Rhomberg
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We have recently rolled from 1.9.0 to 1.10.0 for our {{develop}} version
> semver. Updating the pipeline YML
> {noformat}
> - name: geode-build-version
> type: semver
> source:
> bucket: ((version-bucket))
> driver: gcs
> initial_version: 1.10.0
> json_key: ((!concourse-gcp-key))
> key: ((pipeline-prefix))((geode-build-branch))/version
> {noformat}
> to reference a new version in {{initial_version}} in insufficient to update
> the pipeline's semver, as this value is only used when the file referenced in
> {{key: ((pipeline-prefix))((geode-build-branch))/version}} does not exist.
> We need to examine either a more robust way to store these version files
> (e.g., not using the branch name so that we can guarantee that the file does
> not exist when we update the version) and/or introduce a way to easily bump
> the version that is stored in that file (e.g., through a manually-fired
> Concourse job.) My personal preference would be for the former.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
