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

Add a way to change the SCM release Tag

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • m2release-plugin
    • None

      thanks for the plugin

      • However why do you not propose to use SCM conf job for releasing instead of forcing user to declare SCM parameters in the pom.xml ?
      • BIG PROBLEM : you tag on the SCM with the job name suffixed by the release number. WHY ? Ex :
        INFO Tagging release with the label test-14-standard-web-1_0_0_0_3...

      Instead of tagging my test-14-standard-web with v1_0_0_0_3 as requested in the input release field before the release action.

      So because our SCM check the tag syntax the action is rejected

      It is not the plugin but maven-release-plugin that is responsible of this

      (http://jira.codehaus.org/browse/MRELEASE-159, http://jira.codehaus.org/browse/MRELEASE-150)

      but How can I configure it

      I must give the -Dtag=v1_0_0_0_3 parameter to release:prepare but it will be fine if M2 release plugin could display on the action page, a input field with the SCM tag (with a default value)

      Can I create a issue ?

        1. m2release.patch
          12 kB
        2. m2release.patch
          9 kB
        3. screenshot-1.jpg
          screenshot-1.jpg
          175 kB

          [JENKINS-5171] Add a way to change the SCM release Tag

          fabrice31 created issue -
          fabrice31 made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          fabrice31 made changes -
          Assignee Original: James Nord [ teilo ] New: fabrice31 [ fabrice31 ]

          fabrice31 added a comment -

          I realize the developpement need for choose a tag.
          Please see attached screenshot file.
          Il will include the patch diff later.

          fabrice31 added a comment - I realize the developpement need for choose a tag. Please see attached screenshot file. Il will include the patch diff later.
          fabrice31 made changes -
          Attachment New: screenshot-1.jpg [ 19153 ]
          fabrice31 made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          pierrebocquet made changes -
          Attachment New: m2release.patch [ 19192 ]
          fabrice31 made changes -
          Status Original: Resolved [ 5 ] New: Verified [ 10000 ]

          James Nord added a comment -

          The version needs to be outside of the module iteration as it is a global define not per module - also the patch is very specific to your organization matching the v_ in the tag to compute the version.

          Also can the language be English please to fit with the rest of the plugin.

          If you wish to produce a french localized version can you provide me with a translation of the Strings used in the files under a different JIRA?

          Can you produce a patch which addresses these issues?

          James Nord added a comment - The version needs to be outside of the module iteration as it is a global define not per module - also the patch is very specific to your organization matching the v_ in the tag to compute the version. Also can the language be English please to fit with the rest of the plugin. If you wish to produce a french localized version can you provide me with a translation of the Strings used in the files under a different JIRA? Can you produce a patch which addresses these issues?
          James Nord made changes -
          Status Original: Verified [ 10000 ] New: Reopened [ 4 ]

            Unassigned Unassigned
            fabrice31 fabrice31
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: