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

release-plugin RELEASE_VERSION and DEVELOPMENT_VERSION not available in "After release" build steps

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • release-plugin
    • None
    • Platform: Macintosh, OS: All

      I want to use this plugin in Freestyle-project, but do not succeed calling mvn release:prepare in the "After
      Step". I attach my config.xml, pom.xml and the log-file of an attempt. RELEASE_VERSION and
      DEVELOPMENT_VERSION are not replaced. Pardon me for filing this in core, but there seems to be no
      subcomponent for the release plugin.

      I also tried leaving the parameters out in the step, having the pom.xml configured to use the environment
      variables directly.

        1. config.xml
          2 kB
        2. log
          7 kB
        3. pom.xml
          1 kB

          [JENKINS-3331] release-plugin RELEASE_VERSION and DEVELOPMENT_VERSION not available in "After release" build steps

          Created an attachment (id=630)
          Job-configuration

          Mirko Friedenhagen added a comment - Created an attachment (id=630) Job-configuration

          Created an attachment (id=631)
          Maven2 POM

          Mirko Friedenhagen added a comment - Created an attachment (id=631) Maven2 POM

          Created an attachment (id=632)
          build log

          Mirko Friedenhagen added a comment - Created an attachment (id=632) build log

          I even tried to invoke mvn as a Shell Build Step as well, but this did not work either.

          Mirko Friedenhagen added a comment - I even tried to invoke mvn as a Shell Build Step as well, but this did not work either.

          This is maven-2.0.10. I used Hudson-1.292 started from the commandline via:
          java -jar hudson.war --prefix=/hudson
          with the following plugins installed:
          [mirko@borg Software]$ ls -1 hudson/plugins/*.hpi
          hudson/plugins/ConfigurationSlicing.hpi
          hudson/plugins/audit-trail.hpi
          hudson/plugins/build-timeout.hpi
          hudson/plugins/changelog-history.hpi
          hudson/plugins/cobertura.hpi
          hudson/plugins/dependencyanalyzer.hpi
          hudson/plugins/deploy.hpi
          hudson/plugins/git.hpi
          hudson/plugins/m2release.hpi
          hudson/plugins/mercurial.hpi
          hudson/plugins/port-allocator.hpi
          hudson/plugins/release.hpi
          hudson/plugins/statusmonitor.hpi
          hudson/plugins/violations.hpi

          Mirko Friedenhagen added a comment - This is maven-2.0.10. I used Hudson-1.292 started from the commandline via: java -jar hudson.war --prefix=/hudson with the following plugins installed: [mirko@borg Software] $ ls -1 hudson/plugins/*.hpi hudson/plugins/ConfigurationSlicing.hpi hudson/plugins/audit-trail.hpi hudson/plugins/build-timeout.hpi hudson/plugins/changelog-history.hpi hudson/plugins/cobertura.hpi hudson/plugins/dependencyanalyzer.hpi hudson/plugins/deploy.hpi hudson/plugins/git.hpi hudson/plugins/m2release.hpi hudson/plugins/mercurial.hpi hudson/plugins/port-allocator.hpi hudson/plugins/release.hpi hudson/plugins/statusmonitor.hpi hudson/plugins/violations.hpi

          BTW: same issue on Windows XP with Hudson-1.293, Hudson Release Plugin 1.0 and
          and the latest JDK 1.6:

          • neither in the "Before", the "After" or in the "normal" build step
            %RELEASE_VERSION% seems to be available

          Mirko Friedenhagen added a comment - BTW: same issue on Windows XP with Hudson-1.293, Hudson Release Plugin 1.0 and and the latest JDK 1.6: neither in the "Before", the "After" or in the "normal" build step %RELEASE_VERSION% seems to be available

          Peter Hayes added a comment -

          Fixed this issue in release plugin 1.1. I think a Hudson upgrade must have
          broken the release plugin functionality. I refactored the internals to leverage
          the Hudson parameterization capabilities which should make this much more stable
          during future Hudson releases.

          Peter Hayes added a comment - Fixed this issue in release plugin 1.1. I think a Hudson upgrade must have broken the release plugin functionality. I refactored the internals to leverage the Hudson parameterization capabilities which should make this much more stable during future Hudson releases.

          Peter Hayes added a comment -

          Changing to release component which is now available

          Peter Hayes added a comment - Changing to release component which is now available

          Thanks a lot, this is working for me.

          Mirko Friedenhagen added a comment - Thanks a lot, this is working for me.

            Unassigned Unassigned
            mfriedenhagen Mirko Friedenhagen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: