|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
@Alan - the workaround doesn't quite for us. Here's our scenario:
Jobs:
BuildTrunk - builds the project files from trunk
BuildBranch1_00 - builds project files from branch 1.00
BuildBranch2_00 - builds project files from branch 2.00
PackageTrunk - packages the results of BuildTrunk
PackageBranch1_00 - packages the results of BuildBranch1_00
PackageBranch2_00 - packages the results of BuildBranch2_00
Test - Test is downstream from PackageXYZ
'Test' can run from any of the package jobs, but we create new build and package jobs for each branch. It would be helpful to us to avoid having to duplicate yet another project for each job to maintain our test configurations. What would make this easy is if I could select "Upstream project that triggered this job" in addition to "Upstream build". I see that the information is available on the build page ("Started by ..." on the individual build page). Is it possible to use that same information to implement this feature?