Re: Triggered job - run on same machine?

2013-07-28 Thread Thomas Vestergaard
Hi Bob,

You can use the Node Label Parameter plugin to also send the node. I use this 
extensively to share workspaces between my orchestration- and builder-projects. 

Best regard,

Med venlig hilsen
Thomas Vestergaard Trolle

Sendt fra min iPhone 


On 22/07/2013, at 15.44, Bob Bick bb...@netjets.com wrote:

 Thanks Rob... I realized that they would run in two different subdirectories, 
 and that is why I was passing the subdirectory of the upstream job to the 
 downstream job.
 
 -Original Message-
 From: jenkinsci-users@googlegroups.com 
 [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mandeville, Rob
 Sent: Monday, July 22, 2013 9:42 AM
 To: 'jenkinsci-users@googlegroups.com'
 Subject: RE: Triggered job - run on same machine?
 
 There is no reason that the downstream job will run on the same node as the 
 upstream one.  Even if it happened to do so, they would be in two different 
 subdirectories of the workspace.
 
 You can use the Copy Artifact plugin, or you can make the builders of the 
 downstream job a build step in the upstream job, effectively turning it into 
 one job.
 
 --Rob
 
 -Original Message-
 From: jenkinsci-users@googlegroups.com 
 [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
 Sent: Monday, July 22, 2013 8:18 AM
 To: 'jenkinsci-users@googlegroups.com'
 Subject: Triggered job - run on same machine?
 
 Hi,
 
 I am using the Jenkins Parameterized Trigger Plugin to trigger a downstream 
 job. The downstream job leverages artifacts from the upstream job; hence, I 
 am passing the workspace of the upstream job to the downstream job.
 
 Q. Is it safe to do that? Will it always run on the same node? Or, should you 
 always use the Copy Artifact plugin?
 
 Thanks,
 
 Bob
 
 *** *** ***
 This message contains information which may be confidential and privileged. 
 Unless you are the addressee (or authorized to receive for the addressee), 
 you may not use, copy or disclose to anyone the message or any information 
 contained in the message. If you have received the message in error,  please 
 advise the sender by reply e-mail and delete the message.
 
 -- 
 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.
 
 
 The information in this message is for the intended recipient(s) only and may 
 be the proprietary and/or confidential property of Litle  Co., LLC, and thus 
 protected from disclosure. If you are not the intended recipient(s), or an 
 employee or agent responsible for delivering this message to the intended 
 recipient, you are hereby notified that any use, dissemination, distribution 
 or copying of this communication is prohibited. If you have received this 
 communication in error, please notify Litle  Co. immediately by replying to 
 this message and then promptly deleting it and your reply permanently from 
 your computer.
 
 -- 
 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.
 
 
 
 *** *** ***
 This message contains information which may be confidential and privileged. 
 Unless you are the addressee (or authorized to receive for the addressee), 
 you may not use, copy or disclose to anyone the message or any information 
 contained in the message. If you have received the message in error,  please 
 advise the sender by reply e-mail and delete the message.
 
 -- 
 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.
 
 

-- 
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.




RE: Triggered job - run on same machine?

2013-07-22 Thread Mandeville, Rob
There is no reason that the downstream job will run on the same node as the 
upstream one.  Even if it happened to do so, they would be in two different 
subdirectories of the workspace.

You can use the Copy Artifact plugin, or you can make the builders of the 
downstream job a build step in the upstream job, effectively turning it into 
one job.

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
Sent: Monday, July 22, 2013 8:18 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: Triggered job - run on same machine?

Hi,

I am using the Jenkins Parameterized Trigger Plugin to trigger a downstream 
job. The downstream job leverages artifacts from the upstream job; hence, I am 
passing the workspace of the upstream job to the downstream job.

Q. Is it safe to do that? Will it always run on the same node? Or, should you 
always use the Copy Artifact plugin?

Thanks,

Bob

*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle  Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle  Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
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.




RE: Triggered job - run on same machine?

2013-07-22 Thread Bob Bick
Thanks Rob... I realized that they would run in two different subdirectories, 
and that is why I was passing the subdirectory of the upstream job to the 
downstream job.

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mandeville, Rob
Sent: Monday, July 22, 2013 9:42 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: RE: Triggered job - run on same machine?

There is no reason that the downstream job will run on the same node as the 
upstream one.  Even if it happened to do so, they would be in two different 
subdirectories of the workspace.

You can use the Copy Artifact plugin, or you can make the builders of the 
downstream job a build step in the upstream job, effectively turning it into 
one job.

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
Sent: Monday, July 22, 2013 8:18 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: Triggered job - run on same machine?

Hi,

I am using the Jenkins Parameterized Trigger Plugin to trigger a downstream 
job. The downstream job leverages artifacts from the upstream job; hence, I am 
passing the workspace of the upstream job to the downstream job.

Q. Is it safe to do that? Will it always run on the same node? Or, should you 
always use the Copy Artifact plugin?

Thanks,

Bob

*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle  Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle  Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
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.



*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.