|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-14155) Automatically select/build the latest svn tag (via "List Subversion tags" build params?)
kozlovda.h...@gmail.com (JIRA) Thu, 04 Oct 2012 22:24:18 -0700
- [JIRA] (JENKINS-14155) Automatically select... kozlovda.h...@gmail.com (JIRA)
- [JIRA] (JENKINS-14155) Automatically s... kozlovda.h...@gmail.com (JIRA)
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 in this), 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.