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

Subversion plug in does not support latest change as default value in List Subversion tag(and more) parameter

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Subversion plug in does not support latest change as default value in List Subversion tag(and more) parameter.

      I am using Subversion plug in our jenkins builds.
      I liked List Subversion tag(and more) parameter very much and used to in my jobs.It gives me all artifacts from my SVN URL and i select the one I am looking for during build(manually).But when I am using the polling feature for CI builds, I have to provide the default value in configuration of this parameter.But in polling, I want the latest directory to be selected everytime dynamically from the drop down list it ptovides, not the static default value which keeps changing frequently in my case.
      I am new to this forum and looking for urgent help please.

        Attachments

          Activity

          Hide
          prassawant pras sawant added a comment -

          any luck on this issue .... This is must have feature when you go for complete automation of builds.

          Show
          prassawant pras sawant added a comment - any luck on this issue .... This is must have feature when you go for complete automation of builds.
          Hide
          eugenem Eugene Malihins added a comment - - edited

          Plugin version 2.5.5 (Dec 2015) says:
          issue #14155 Automatically select and build the latest tag (via "List Subversion tags" build params)

          However when using SCM polling from Pipeline script or Poll SCM section this does not work and the previously manually selected SVN_TAG is being used.

          EDIT: seems I was wrong/not enough coffee. SCM Polling+List Subversion tags does indeed pass latest SVN_TAG to my pipeline script.

          EDIT_2: OK, I figured where the issue was. With Pipeline plugin you cannot re/set SVN_URL variable at the end of the script, so the 1st time pipeline runs with the correct "../tags" URL. The second time after "../tags/{$SVN_TAG}" were already expanded in the previous run, the URL becomes, for example, "../tags/1.1.5" and polling continues on this URL.

          This is a separate issue concerning Pipeline plugin.

          Show
          eugenem Eugene Malihins added a comment - - edited Plugin version 2.5.5 (Dec 2015) says: issue #14155 Automatically select and build the latest tag (via "List Subversion tags" build params) However when using SCM polling from Pipeline script or Poll SCM section this does not work and the previously manually selected SVN_TAG is being used. EDIT: seems I was wrong/not enough coffee. SCM Polling+List Subversion tags does indeed pass latest SVN_TAG to my pipeline script. EDIT_2: OK, I figured where the issue was. With Pipeline plugin you cannot re/set SVN_URL variable at the end of the script, so the 1st time pipeline runs with the correct "../tags" URL. The second time after "../tags/{$SVN_TAG}" were already expanded in the previous run, the URL becomes, for example, "../tags/1.1.5" and polling continues on this URL. This is a separate issue concerning Pipeline plugin.

            People

            • Assignee:
              Unassigned
              Reporter:
              s_007 S B
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: