Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-57690

Support more sophisticated versioning

XMLWordPrintable

      At the moment, the @Library annotation supports the exact tag from a repository. This is great, but simplistic. As a team who are semantically versioning the shared library and regularly pushing out patch and minor versions, the overhead of expecting teams to constantly update their Jenkinsfiles is a little unfair. We want teams to be able to pin to a major version but be able to accept minor or patch version updates.

      For example, the following syntax should be valid: @Library('library@v0.1.'). It should find the latest tag matching v0.1.* and pull in that version.

          [JENKINS-57690] Support more sophisticated versioning

          Jesse Glick added a comment -

          You could simply make a policy of creating an extra tag (or several) with simpler names whenever pushing an update. This is the typical workflow for publishing GitHub Actions, for example: push tags v5, v5.1, and v5.1.7 at once. (Assuming the Git server is configured to permit tags to be overwritten.)

          Jesse Glick added a comment - You could simply make a policy of creating an extra tag (or several) with simpler names whenever pushing an update. This is the typical workflow for publishing GitHub Actions, for example: push tags v5 , v5.1 , and v5.1.7 at once. (Assuming the Git server is configured to permit tags to be overwritten.)

            Unassigned Unassigned
            chriscooney chris cooney
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: