On Thu, Oct 30, 2014 at 1:31 PM, Ross Aribi wrote:
> You have two jobs, Job1 calling Job2. The parameter $JOB_NAME is local to
> each job, so in Job2 the value of $JOB_NAME is Job2.
> Add an additional param in Job1 ($JOB_1_NAME=$JOB_NAME) and use it in Job2.
That's exactly what I'm doing, these
On Thu, Oct 30, 2014 at 11:56 AM, T. Anthony Rabaa wrote:
> If you're building on the same node, why not pass in the full path to the
> libraries as a parameter?
Good idea. I'll give that a go.
Cheers
Adam
--
You received this message because you are subscribed to the Google Groups
"Jenkins
You have two jobs, Job1 calling Job2. The parameter $JOB_NAME is local to
each job, so in Job2 the value of $JOB_NAME is Job2.
Add an additional param in Job1 ($JOB_1_NAME=$JOB_NAME) and use it in Job2.
FYI, any value that's empty means that the parameter value is undefined.
Check spellings too.
If you're building on the same node, why not pass in the full path to the
libraries as a parameter?
> On Oct 27, 2014, at 11:04 AM, Adam Mercer wrote:
>
> Hi
>
> Anyone? Surely the plugin shouldn't be stripping information when
> passing it on to downstream jobs?
>
> Cheers
>
> Adam
>
>> O
Hi
Anyone? Surely the plugin shouldn't be stripping information when
passing it on to downstream jobs?
Cheers
Adam
On Thu, Oct 23, 2014 at 5:15 PM, Adam Mercer wrote:
> Hi
>
> I'm trying to tie a couple of jobs together using the Parametrized
> Trigger Plugin and am running into problems with
Hi
Hi
I'm trying to tie a couple of jobs together using the Parametrized
Trigger Plugin and am running into problems with the second job
finding the libraries built by the first job.
When the first job completes successfully I trigger a build of the
second job, I'm forcing it to use the same nod
