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

Release modifies the job goals which leads to a new release on every 'normal' build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • m2release-plugin
    • None
    • Hudson 1.363, Maven Release Plugin 0.4.0

      Hi,

      We had suddenly one Job which was creating a new release on every build. We checked the config and saw that the following goals were configured:

      -Dproject.dev.XXXXX.server:logging-server-generator-ear=2.0.1-SNAPSHOT
      -Dproject.rel.XXXXX.server:logging-server-generator=2.0.0
      Dproject.rel.XXXXX.server:server-generator_moduleList=2.0.0
      -Dproject.dev.XXXXX.server:logging-server-generator=2.0.1-SNAPSHOT
      -Dproject.rel.XXXXX.server:common-logging-server-generator-root-pom=2.0.0
      -Dproject.dev.XXXXX.common-logging-server-generator-root-pom=2.0.1-SNAPSHOT
      -Dproject.rel.XXXXX.logging-server-generator-ear=2.0.0
      Dproject.dev.XXXXX.server:server-generator_moduleList=2.0.1-SNAPSHOT
      -Dresume=false release:prepare release:perform

      I assume that this change was not made by one of our users. It seems that the release plugin just modifies the actual goals and switch it back after the release.

      If this is the case I think there should be another way used as it obviously does not work always and a 'release per checkin' is definitely a big problem (especially as every release contains a checkin and triggers a new build)

      Could someone confirm that this is the way the plugin works?
      If this is the way: please change it!

      Regards

      Michael

          [JENKINS-6985] Release modifies the job goals which leads to a new release on every 'normal' build

          James Nord added a comment -

          "It seems that the release plugin just modifies the actual goals and switch it back after the release."
          Yes
          "a 'release per checkin' os definatley a big problem" - this is the only way it can work.

          This is a Maven Release and Maven will check in your code to create the tag (not all SCMs can create a tag from no-commited data.

          "Could someone confirm that this is the way the plugin works?"
          Yes
          "If this is the way: please change it!"
          No - please raise a new issue and supply logs for the builds from when it was working (creating snapshot builds) to when it failed to return the goals back.

          James Nord added a comment - "It seems that the release plugin just modifies the actual goals and switch it back after the release." Yes "a 'release per checkin' os definatley a big problem" - this is the only way it can work. This is a Maven Release and Maven will check in your code to create the tag (not all SCMs can create a tag from no-commited data. "Could someone confirm that this is the way the plugin works?" Yes "If this is the way: please change it!" No - please raise a new issue and supply logs for the builds from when it was working (creating snapshot builds) to when it failed to return the goals back.

            Unassigned Unassigned
            micha4311 micha4311
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: