Quantcast

Promoted builds plugin and custom workspace

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Promoted builds plugin and custom workspace

Matthew.Webber
We use the promoted builds plugin, and I've just discovered an annoying difference in behaviour depending on whether a custom workspace is used.

Previously, I used a custom workspace: ${JENKINS_WORKSPACE_PARENT}/${JOB_NAME}
When a promotion ran, the working directory was set to ${JENKINS_WORKSPACE_PARENT}/${JOB_NAME}/promotion/<name of promotion>
Ie, it appends /promotion/<name of promotion> to the workspace path.

I then set up a similar job but without a custom workspace
When a promotion ran, the working directory was set to the original workspace path, the "/promotion/<name of promotion>" was not there appended.

This caused no end of confusion, but more importantly, why the difference? Is that intentional or a bug?
I'm using  2.6.1 of the promoted builds plugin (the latest), Jenkins 1.472.

Has anyone else encountered this?

Thanks
Matthew



--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Promoted builds plugin and custom workspace

cjo9900

There is no change that has occurred as the promotion is its own job, and therefore has its own ${JOB_NAME} 
which is parent_jobname/promotions/< promotion_name>

So the behaviour is consistent when using the custom workspace option.
If you read the wiki page [1] for the plugin there is a warning on the workspace that is used.


Chris

On Friday, July 27, 2012 4:59:29 PM UTC+1, (unknown) wrote:
We use the promoted builds plugin, and I've just discovered an annoying difference in behaviour depending on whether a custom workspace is used.

Previously, I used a custom workspace: ${JENKINS_WORKSPACE_PARENT}/${JOB_NAME}
When a promotion ran, the working directory was set to ${JENKINS_WORKSPACE_PARENT}/${JOB_NAME}/promotion/<name of promotion>
Ie, it appends /promotion/<name of promotion> to the workspace path.

I then set up a similar job but without a custom workspace
When a promotion ran, the working directory was set to the original workspace path, the "/promotion/<name of promotion>" was not there appended.

This caused no end of confusion, but more importantly, why the difference? Is that intentional or a bug?
I'm using  2.6.1 of the promoted builds plugin (the latest), Jenkins 1.472. 

Has anyone else encountered this?

Thanks
Matthew



--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom




Loading...