-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Windows, Linux
When triggering a downstream build project using current build parameters a defined string parameter in the upstream triggering project is not evaluated if entered into the list subversion tags default of the downstream project.
The intent is to have a subversion tag specified in an upstream project used in downstream projects to setup the workspace. This arrangement is intended to allow the upstream project to define the svn tag for all downstream projects and still allow the dowmstream projects to be executed directly without any reconfiguration.
[JENKINS-17476] parameterized-trigger List Subversion tags default value set to a current build parameter not evaluated
ikedam
added a comment - I could not get your point.
Please report followings:
- Your subversion repository layout.
- How do you configured projects.
- What is the intended behavior. That is, what urls and revisions you want checked out.
- The actual behavior. That is, what urls and revisions are checked out.
- Attach build.xml of builds if that doesn't matter.
ikedam
added a comment - I could not get your point.
Please report followings:
Your subversion repository layout.
How do you configured projects.
What is the intended behavior. That is, what urls and revisions you want checked out.
The actual behavior. That is, what urls and revisions are checked out.
Attach build.xml of builds if that doesn't matter.
>In what version of Jenkins is this bug occurring or you do miss a feature, want an improvement? If this issue is (likely) related to plugins, please also include >the plugins' versions.
1.501
>What environment are you using? Hint: You should attach the information from http://SERVER/systemInfo.
various clients, windows redhat, ubuntu, centos, aix, solairus
>How are you running Jenkins?
master with slave hosts
>Using the executable war like java -jar jenkins.war
no
>Using another container as Tomcat or Jetty.
no
>Have you specified additional parameters for the Java VM (Heapspace etc.)?
no
>Did you just install the deb or rpm?
deb
>With which Java VM (Oracle, IBM etc.)?
sun 1.6 and oracle 1.7
>On which operating system? 32- or 64-bit?
both
>Include stacktraces from the log if any.
n/a
>Did this error start occurring after an upgrade?
no, from first use
>What version did you upgrade to/from?
n/a
>Is this your first install?
yes
>If this is an issue in the collaboration with another system (e.g. a SCM), please also provide the type and the version of the other system
n/a