[GEODE-6460] geode-build-version does not automatically update with a new version

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0
• Assignee: Unassigned
• Reporter: Patrick Rhomberg
• Created: 27/Feb/19 19:01
• Updated: 05/Feb/20 23:18
• Resolved: 05/Feb/20 23:18

Description

We have recently rolled from 1.9.0 to 1.10.0 for our develop version semver. Updating the pipeline YML

- 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

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.

Issue Links

• links to: GitHub Pull Request #3250
• links to: GitHub Pull Request #3286