![]() |
|
|
|
|
Change By:
|
Tom Ghyselinck
(02/Apr/14 7:45 AM)
|
|
Issue Type:
|
New Feature
Improvement
|
|
Description:
|
*Problem*
When using Subversion's
_
"list tags"
_
parameter, the default value associated with a
_
"list tags"
_
parameter is the only one taken into account for automatically triggered builds.
When using the parameter in a subversion repository for the source code, the automatic build (e.g. periodic build) fails when there is no default value defined.
e.g. defining
*For example*
Defining {{
VERSION
}} _
"list tags"
_
parameter without default value
and using it as "
{{
svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
}}
" in the source code
makes our automatic build fail!
The exception from the console log is:
{code}
Location 'svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION' does not exist
Switching from svn+ssh://svn.mycompany.com/repository_root/branches/1.2.3 to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
Switching to svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION at revision '2013-09-12T01:18:56.750 +0200'
ERROR: Failed to update svn+ssh://svn.mycompany.com/repository_root/branches/$VERSION
{code}
*Proposal*
I expect the plugin to look in all (matching) "tags" and use/build the tag which has the latest changes.
Although, when I select
_*
"Sort newest first"
*_
or
_*
"Sort Z to A"
*_
, I expect the
_*
first "tag"
*_
in the sorted list
to be
checked
_checked
for
changes
changes_ *
and
used
* _used_
in the
automatic
_automatic
triggered
build
build_
.
Does anyone have other comments on this issue?
This is an important issue for us, because we use multiple active branches and we want to build every branch automatically when there are changes!
|
|
Component/s:
|
parameterized-trigger
|
|
Component/s:
|
parameters
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
