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

Default versioning mode is not getting picked while invoking the maven release build

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • m2release-plugin
    • None
    • Ubuntu OS

      Hi,
      After selecting the "Default versioning mode" as "none", when we try to perform maven release build, we are not getting the options for "versioning mode".
      Even we try to change the "Default versioning mode" to "Specify versions", it is not behaving properly.

        1. 1.JPG
          1.JPG
          15 kB
        2. 2.JPG
          2.JPG
          21 kB

          [JENKINS-15298] Default versioning mode is not getting picked while invoking the maven release build

          Jorg Heymans added a comment -

          seeing this as well, the selected value in the dropdown is ignored. In fact when you reopen the configuration page you'll see that the value is always reset back to 'None'

          Jorg Heymans added a comment - seeing this as well, the selected value in the dropdown is ignored. In fact when you reopen the configuration page you'll see that the value is always reset back to 'None'

          nickithewatt added a comment - - edited

          I can confirm that this is still a problem - using version 1.525 of jenkins and latest version (0.12.0) of m2release plugin

          nickithewatt added a comment - - edited I can confirm that this is still a problem - using version 1.525 of jenkins and latest version (0.12.0) of m2release plugin

          Anders Hammar added a comment -

          What about the 'autoVersionSubmodules' param configuration of maven-release-plugin from the pom, shouldn't it be honored instead?
          I guess it's a question about which path to take here. Either the m2release plugin is just a shell around m-release-p and uses it's configuration as much as possible or it replaces the configuration of m-release-p. Pros and cons with both paths.

          Anders Hammar added a comment - What about the 'autoVersionSubmodules' param configuration of maven-release-plugin from the pom, shouldn't it be honored instead? I guess it's a question about which path to take here. Either the m2release plugin is just a shell around m-release-p and uses it's configuration as much as possible or it replaces the configuration of m-release-p. Pros and cons with both paths.

          The autoVersionSubmodules option has the following explanation:
          "Whether to automatically assign submodules the parent version. If set to false, the user will be prompted for
          the version of each submodules."
          This would correspond to the "Specify one version for all modules" versioning mode (which seems to be the default behaviour if interactive mode is switched off for the maven plugin).
          It would however be very useful if one could use "Specify version(s)" to be able to specify the (different) versions of all submodules in one view. We really miss this option at the moment.

          Frank van Eerden added a comment - The autoVersionSubmodules option has the following explanation: "Whether to automatically assign submodules the parent version. If set to false, the user will be prompted for the version of each submodules." This would correspond to the "Specify one version for all modules" versioning mode (which seems to be the default behaviour if interactive mode is switched off for the maven plugin). It would however be very useful if one could use "Specify version(s)" to be able to specify the (different) versions of all submodules in one view. We really miss this option at the moment.

          Guy Rooms added a comment -

          Same problem here on:
          jenkins: 1.564
          Maven release plugin: 0.14.0

          Guy Rooms added a comment - Same problem here on: jenkins: 1.564 Maven release plugin: 0.14.0

          Code changed in jenkins
          User: Dennis Kieselhorst
          Path:
          src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly
          http://jenkins-ci.org/commit/m2release-plugin/db480ec581e6039bbb0c3749bb21cd32d4266da0
          Log:
          JENKINS-15298: Remove until implemented

          Currently this setting has no effect and is confusing.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Dennis Kieselhorst Path: src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly http://jenkins-ci.org/commit/m2release-plugin/db480ec581e6039bbb0c3749bb21cd32d4266da0 Log: JENKINS-15298 : Remove until implemented Currently this setting has no effect and is confusing.

          Code changed in jenkins
          User: James Nord
          Path:
          src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly
          http://jenkins-ci.org/commit/m2release-plugin/2f2865cffdd7e4be2a60156f245fabc9508d870b
          Log:
          Merge pull request #28 from deki/patch-1

          JENKINS-15298: Remove defaultVersioningMode until re-implemented

          Compare: https://github.com/jenkinsci/m2release-plugin/compare/78023d940d1b...2f2865cffdd7

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: James Nord Path: src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly http://jenkins-ci.org/commit/m2release-plugin/2f2865cffdd7e4be2a60156f245fabc9508d870b Log: Merge pull request #28 from deki/patch-1 JENKINS-15298 : Remove defaultVersioningMode until re-implemented Compare: https://github.com/jenkinsci/m2release-plugin/compare/78023d940d1b...2f2865cffdd7

            lebrame57 alexis oliot
            vishal_vsh1 vishal sahasrabuddhe
            Votes:
            16 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated: