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

M2 Release plugin ignores parameters from a parameterized build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • m2release-plugin
    • None

      We have parameterized build tasks where we specify the branch part of our svn repository so we can build from the trunk or a branch.
      This plugin does not allow us to specify this parameter and so always does a checkout from the trunk (trunk is the default value for the parameter).
      This means that we cannot release from a branch.

      Please fix this so that parameters can be specified.

          [JENKINS-10127] M2 Release plugin ignores parameters from a parameterized build

          Dominik Bartholdi added a comment -

          send a pull request: https://github.com/jenkinsci/m2release-plugin/pull/3

          Dominik Bartholdi added a comment - send a pull request: https://github.com/jenkinsci/m2release-plugin/pull/3

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: jtnord
          Path:
          .gitignore
          src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java
          src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseAction/index.jelly
          http://jenkins-ci.org/commit/m2release-plugin/a1ddf1da50f48bb7eabee11871ea33e25948262e
          Log:
          Merge pull request #3 from imod/build-params

          add support for build parameters in maven release

          In addition to the normal release parameters, the 'normal' build parameters are shown and can be modified too before triggering a release build.

          This fixes or supports the following currently open issues:

          • JENKINS-10127: M2 Release plugin ignores parameters from a parameterized build
          • JENKINS-4690: Be able to arbitrary paramterize m2 releases
          • JENKINS-4500: Make it possible to select a node to do the release on (together with the nodelabel-plugin)
          • JENKINS-4958: add switch for -DdryRun=true

          Compare: https://github.com/jenkinsci/m2release-plugin/compare/418a96c...a1ddf1d

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: jtnord Path: .gitignore src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseAction/index.jelly http://jenkins-ci.org/commit/m2release-plugin/a1ddf1da50f48bb7eabee11871ea33e25948262e Log: Merge pull request #3 from imod/build-params add support for build parameters in maven release In addition to the normal release parameters, the 'normal' build parameters are shown and can be modified too before triggering a release build. This fixes or supports the following currently open issues: JENKINS-10127 : M2 Release plugin ignores parameters from a parameterized build JENKINS-4690 : Be able to arbitrary paramterize m2 releases JENKINS-4500 : Make it possible to select a node to do the release on (together with the nodelabel-plugin) JENKINS-4958 : add switch for -DdryRun=true Compare: https://github.com/jenkinsci/m2release-plugin/compare/418a96c...a1ddf1d

            jsirex jsirex
            pgeyman Piers Geyman
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: