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

Proposed version number is not up-to-date when only releasing

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • m2release-plugin
    • None
    • Jenkins on linux

      When a Maven release is performed right after a previous one, then the proposed Release Version and Development Version are still the same as the previous ones.

      For the versions to be updated, a build must be executed between two Maven releases.

          [JENKINS-14959] Proposed version number is not up-to-date when only releasing

          Patrick Roth created issue -
          Patrick Roth made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Summary Original: Propsed versin number is not up-to-date when only releasing New: Proposed version number is not up-to-date when only releasing

          Emilio Jose Mena Cebrian added a comment - - edited

          I suspect that the versions aren't the only outdated information .

          Maybe module dependencies should be updated as well after a successful build if the release task changes the pom in order to fix SNAPSHOTS versions (using the "prepare-with-pom" goal)

          Is it possible to reparse poms after releasing the version. I've seen MavenModuleSetBuildExecution.parsePoms method, but it isn't public.

          Emilio Jose Mena Cebrian added a comment - - edited I suspect that the versions aren't the only outdated information . Maybe module dependencies should be updated as well after a successful build if the release task changes the pom in order to fix SNAPSHOTS versions (using the "prepare-with-pom" goal) Is it possible to reparse poms after releasing the version. I've seen MavenModuleSetBuildExecution.parsePoms method, but it isn't public.

          James Nord added a comment -

          even if you could parse the poms at the end of the build but it won't help.

          e.g.
          perform the release (in jenkins)
          parse pom
          dev checks in 5000 changes.
          jenkins is not polling and not building this source code

          next release (info is outdated).

          The buildwrappers are called before the code checkout so I doubt there is much that can be done to ensure that the numbers (and module list) is always correct.

          James Nord added a comment - even if you could parse the poms at the end of the build but it won't help. e.g. perform the release (in jenkins) parse pom dev checks in 5000 changes. jenkins is not polling and not building this source code next release (info is outdated). The buildwrappers are called before the code checkout so I doubt there is much that can be done to ensure that the numbers (and module list) is always correct.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 145660 ] New: JNJira + In-Review [ 176417 ]
          James Nord made changes -
          Assignee Original: James Nord [ teilo ]

            Unassigned Unassigned
            redparrot Patrick Roth
            Votes:
            9 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: