• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • maven-plugin
    • None

      For Maven builds an environment variable POM_VERSION is present set to the version of the pom. This is useful to create a PIPELINE_VERSION from.
      But usually this is set to a SNAPSHOT version and in a pipeline SNAPSHOTS should not be used. So introduce a token macro which lookup the POM_VERSION and optionally remove the -SNAPSHOT part. Then it is possible to create PIPELINE_VERSION with $POM_VERSION.$BUILD_NUMBER.
      If the pom version is changed you dont need to change any configuration in Jenkins.

          [JENKINS-23249] TokenMacro for POM_VERSION

          Patrik Boström created issue -
          Patrik Boström made changes -
          Description Original: For Maven builds an environment variable POM_VERSION is present set to the version of the pom. This is useful to create a PIPELINE_VERSION from.
          But usually this is set to a SNAPSHOT version and in a pipeline SNAPSHOTS should not be used. So introduce a token macro which lookup the POM_VERSION and optionally remove the -SNAPSHOT part. Then it is possible to create PIPELINE_VERSION with $POM_VERSION.$BUILD_NUMBER. If the pom version is changed you dont need to change any configuration in Jenkins
          New: For Maven builds an environment variable POM_VERSION is present set to the version of the pom. This is useful to create a PIPELINE_VERSION from.
          But usually this is set to a SNAPSHOT version and in a pipeline SNAPSHOTS should not be used. So introduce a token macro which lookup the POM_VERSION and optionally remove the -SNAPSHOT part. Then it is possible to create PIPELINE_VERSION with $POM_VERSION.$BUILD_NUMBER.
          If the pom version is changed you dont need to change any configuration in Jenkins.

          Is this really an issue that belongs to the delivery-pipeline plugin? Is it not more about the maven-plugin?

          Kohsuke Kawaguchi added a comment - Is this really an issue that belongs to the delivery-pipeline plugin? Is it not more about the maven-plugin ?

          Changing component

          Patrik Boström added a comment - Changing component
          Patrik Boström made changes -
          Component/s New: maven2 [ 15487 ]
          Component/s Original: delivery-pipeline [ 18134 ]
          Priority Original: Major [ 3 ] New: Minor [ 4 ]

          Create PR with a proposed implementation:
          https://github.com/jenkinsci/maven-plugin/pull/25

          Patrik Boström added a comment - Create PR with a proposed implementation: https://github.com/jenkinsci/maven-plugin/pull/25
          Jenkins IRC Bot made changes -
          Component/s New: maven-plugin [ 16033 ]
          Component/s Original: maven2 [ 15487 ]

          Radek Antoniuk added a comment - - edited

          LGTM, this would be really useful connected with Delivery Pipeline plugin.
          jglick I can see you are very active in this plugin, could you take a look at PR #47?

          Radek Antoniuk added a comment - - edited LGTM, this would be really useful connected with Delivery Pipeline plugin. jglick I can see you are very active in this plugin, could you take a look at PR #47?
          Radek Antoniuk made changes -
          Remote Link New: This issue links to "PR47 (Web Link)" [ 12953 ]
          Radek Antoniuk made changes -
          Assignee New: Jesse Glick [ jglick ]

            Unassigned Unassigned
            patbos Patrik Boström
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: