![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
jenkins-multijob-plugin |
|
Created:
|
11/Nov/13 12:12 PM
|
|
Description:
|
The following behavior seen under multijob is different then similar scenarios created with chained jobs.
1. Create multijob project (A) as paramertized job
2. Create a param using the build native params(PARAM=$BUILD_ID)
3. Create another paramertized job (B)
4. Add B as subjob of A
5. In A add predefined parameter to B (PARAM=$PARAM)
6. Echo in shell of both scripts $PARAM
Expected results:
the values of $PARAM will be the same in both A and B (values is A's build_id)
Actual results:
value is different in A and B, B re evaluates $PARAM and gives it it's own $BUILD_ID
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Lior Boord
|
|
|
|
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/groups/opt_out.
