Re: incorrect parameters passed to downstream build with Parameterized Trigger plugin

2013-05-15 Thread cjo
As I commented in your other thread, a Matrix job runs 
the parametrized trigger on the parent job once only and not for each 
configuration used.
This is not a bug but intended design.

Note that the value of $WORKSPACE is incorrect on master as well, (try 
printing the variable out in a build step of job A)
as the three values will be similar to those below on the different 
machines(including the axis label)
master - /var/lib/jenkins/workspace/A
linux- /var/lib/jenkins/workspace/A/label-linux/
mac-Slave_workspace/A/label-mac/
windows-Slave_workspace\A\label-windows\

As you seem to be testing this out, I assume that the two jobs will need to 
share a workspace/files.
What is the problem that you are trying to solve so that others can 
suggested a better solution the just sharing workspaces.

As it might be easier for Job A to artifact the files required for Job B, 
and Job B to copy those when run using the copy artifact plugin. 
This normally removes other issues related to using the same workspace for 
multiple jobs, when they get out of sync i.e. when job B only runs once for 
multiple runs of job A.

Chris.

On Wednesday, 15 May 2013 00:03:56 UTC+1, Dan Tenenbaum wrote:

 Hi,
  
 I have two multi-configuration projects, A and B.
 Each job is configured to run on the same three nodes: the master (linux) 
 and mac and windows slaves.

 Project A is set up to trigger a build of B when A builds successfully, 
 passing it the following predefined parameters (using the Parameterized 
 Trigger plugin):

 PREV_WORKSPACE=$WORKSPACE
 PREV_JOB_NAME=$JOB_NAME
 PREV_BUILD_TAG=$BUILD_TAG
 PREV_BUILD_ID=$BUILD_ID
 PREV_BUILD_DISPLAY_NAME=$BUILD_DISPLAY_NAME

 For now, project B just calls a shell script that prints out some of these 
 values. 
 On the master, B says that $PREV_WORKSPACE is /var/lib/jenkins/workspace/A
 which is correct. 
 On the other nodes, though, it ALSO gives the same value for 
 $PREV_WORKSPACE which is WRONG...the workspace path is different on each 
 node.

 Is this a bug? Can it be fixed?
 Thanks,
 Dan





-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




incorrect parameters passed to downstream build with Parameterized Trigger plugin

2013-05-14 Thread Dan Tenenbaum
Hi,

I have two multi-configuration projects, A and B.
Each job is configured to run on the same three nodes: the master (linux) 
and mac and windows slaves.

Project A is set up to trigger a build of B when A builds successfully, 
passing it the following predefined parameters (using the Parameterized 
Trigger plugin):

PREV_WORKSPACE=$WORKSPACE
PREV_JOB_NAME=$JOB_NAME
PREV_BUILD_TAG=$BUILD_TAG
PREV_BUILD_ID=$BUILD_ID
PREV_BUILD_DISPLAY_NAME=$BUILD_DISPLAY_NAME

For now, project B just calls a shell script that prints out some of these 
values. 
On the master, B says that $PREV_WORKSPACE is /var/lib/jenkins/workspace/A
which is correct. 
On the other nodes, though, it ALSO gives the same value for 
$PREV_WORKSPACE which is WRONG...the workspace path is different on each 
node.

Is this a bug? Can it be fixed?
Thanks,
Dan



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.