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

Automatically select/build the latest svn tag (via "List Subversion tags" build params?)

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Minor Minor
    • subversion-plugin
    • None

      My use case is that I want jenkins to automatically build new tags when they are created, so jenkins should somehow automcatically choose the latest tag.

      The "List Subversion tags" already allows to limit the tags to only 1, and with "Sort newest first" it actually shows the latest tag, but this cannot be chosen automatically.

      To select the latest tag automatically I can think of an option "Select newest automatically".

      This build param (newest tag) should be used in scm polling and also when a manual build is triggered.

          [JENKINS-14155] Automatically select/build the latest svn tag (via "List Subversion tags" build params?)

          Martin Grotzke created issue -
          Martin Grotzke made changes -
          Description Original: The "List Subversion tags" already allows to limit the displayed tags to only 1, and with "Sort newest first" it actually shows the latest tag.

          My use case is that I want jenkins to automatically build new tags when they are created, so jenkins should somehow automcatically choose the latest tag (e.g. via some "Select newest"?).

          This param (newest tag) should be used in scm polling and also when a manual build is triggered.
          New: My use case is that I want jenkins to automatically build new tags when they are created, so jenkins should somehow automcatically choose the latest tag.

          The "List Subversion tags" already allows to limit the tags to only 1, and with "Sort newest first" it actually shows the latest tag, but this cannot be chosen automatically.

          To select the latest tag automatically I can think of an option "Select newest automatically".

          This build param (newest tag) should be used in scm polling and also when a manual build is triggered.

          How would this play with other parameters? It would seem that either this would have to be the only parameter, or all the other parameters would have to have valid defaults for a build to automatically launch.

          Daniel Kirkdorffer added a comment - How would this play with other parameters? It would seem that either this would have to be the only parameter, or all the other parameters would have to have valid defaults for a build to automatically launch.

          Yes, that would be the consequence. So this would have to be proper documented.

          Martin Grotzke added a comment - Yes, that would be the consequence. So this would have to be proper documented.

          Dmitry Kozlov added a comment - - edited

          Hi Guys,

          This feature would be highly appreciated, as it allows to properly automate RC tags processing.

          Regarding other parameters - I think the default logic (we already have) should work fine here.
          We're already able to configure parameterized job to run on scm change using default param values. What makes it different when [List Subversion tags] field is used?
          I.e. if there is a triggered build with validating params and no proper defaults provided - it just fails and doesn't start till next triggering event like SCM change (or new tag created), otherwise default values applied.

          Actually, what I'd be looking for is a NewTag-SCMTrigger with tag base/mask configurable similar to [List Subversion tags].

          Think of it as of traditional SCM polling build trigger. It's just that we use "new tag" category rather than "new commits".

          (Sounds like a separate feature request that deserves new JIRA item )

          But this particual JIRA implementation should also be helpfull as it allows to trigger builds remotely, e.g. from script.

          Kind regards,
          Dmitry.

          Dmitry Kozlov added a comment - - edited Hi Guys, This feature would be highly appreciated, as it allows to properly automate RC tags processing. Regarding other parameters - I think the default logic (we already have) should work fine here. We're already able to configure parameterized job to run on scm change using default param values. What makes it different when [List Subversion tags] field is used? I.e. if there is a triggered build with validating params and no proper defaults provided - it just fails and doesn't start till next triggering event like SCM change (or new tag created ), otherwise default values applied. Actually , what I'd be looking for is a NewTag-SCMTrigger with tag base/mask configurable similar to [List Subversion tags] . Think of it as of traditional SCM polling build trigger. It's just that we use "new tag" category rather than "new commits" . (Sounds like a separate feature request that deserves new JIRA item ) But this particual JIRA implementation should also be helpfull as it allows to trigger builds remotely, e.g. from script. Kind regards, Dmitry.

          Hi Guys,
          I implemented most of the items of this tickets (https://github.com/jenkinsci/subversion-plugin/pull/40/commits).

          But I'm still missing the described option "Select newest automatically". Can someone add this option?

          On my implementation when you limit the tags to only 1, and with "Sort newest first" it's automatically enabled.

          Kind regards,
          Pedro

          Pedro Goncalves added a comment - Hi Guys, I implemented most of the items of this tickets ( https://github.com/jenkinsci/subversion-plugin/pull/40/commits ). But I'm still missing the described option "Select newest automatically". Can someone add this option? On my implementation when you limit the tags to only 1, and with "Sort newest first" it's automatically enabled. Kind regards, Pedro
          Yoichi Nakayama made changes -
          Link New: This issue is duplicated by JENKINS-19560 [ JENKINS-19560 ]
          Yoichi Nakayama made changes -
          Link New: This issue is duplicated by JENKINS-14092 [ JENKINS-14092 ]
          Yoichi Nakayama made changes -
          Link Original: This issue is duplicated by JENKINS-14092 [ JENKINS-14092 ]
          Yoichi Nakayama made changes -
          Link New: This issue is related to JENKINS-14092 [ JENKINS-14092 ]

            recena Manuel Recena Soto
            martin_grotzke Martin Grotzke
            Votes:
            10 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: