If the job is not configured to ruin on the master and the master is configured to only run jobs specifically assigned to it, then the job should not run on master. There will still be a clone on the master, but the job won't run there.
Working directory name had changed with the most recent plugin release. The percent character is not used in the directory name now. Mark Waite On Tue, Oct 4, 2016, 12:33 AM vishad alekh <[email protected]> wrote: Hi Mark, Thanks for your reply. 1- I have not configured anything for my master node and still it creates on master. So does that mean it will be running the same way on master node. 3- actually my GIT branch structure is something like release/ABC. Now when a job is created with this name it gets a format like release@%2FABC. This format becomes very difficult to handle on Linux boxes. Hence I was wondering if there is anyway to change the name and keep it more easy to use. Thanks and Regards Vishad Alekh Sent from my BlackBerry 10 smartphone. *From: *Mark Waite *Sent: *Monday 3 October 2016 5:29 PM *To: *[email protected] *Reply To: *[email protected] *Subject: *Re: Pipeline Issue 1 - The master agent needs to identify which branches contain a Jenkinsfile and match the branch selection criteria you provided. In order to do that, the master agent clones the repository and uses that clone for the work on the master agent 3 - I've found no way to change the name of the job which is created. Can you describe how you envision using that changed name, and how you would avoid job name collisions? Mark Waite On Mon, Oct 3, 2016 at 12:03 AM vishad alekh <[email protected]> wrote: Hi Sam, Thanks for your reply. Can anyone please assist me with number 1 and number 3. Thanks and Regards Vishad Alekh Sent from my BlackBerry 10 smartphone. *From: *Sam K *Sent: *Monday 3 October 2016 9:50 AM *To: *Jenkins Users *Reply To: *[email protected] *Subject: *Re: Pipeline Issue Hi Vishad I am not too sure about the 1 and 3, but regarding 2, I've seen that happen. No matter how many times you remove those @ folders, they come back. I've left those alone and I've noticed that Jenkins will manage them accordingly. They don't keep growing in number either. I have run a pipeline job which has been executed about 200 times and I see like 5 or 6 of those @tmp folders. I believe Jenkins uses them for keeping track of parallel threads. They are usually empty or have very little in them. So no need to worry about them. :) On Saturday, October 1, 2016 at 12:20:42 PM UTC-7, vishad alekh wrote: Hi All, Please assist me with below :- I have created a multipipeline job with Jenkinsfile. This job will search for Jenkinsfile in GIT repo and will make the job accordingly. In this file I have configured it on the some other node apart from the one where Jenkins is running. Doubts :- 1- when this new job gets created, I can see a folder with the same name on master server as well. How come it's getting created on master node too.ideally I think it should only be in that node which is defined in Jenkinsfile. 2- It creates a folder with the name @2 or @temp. What are these? 3-how can we change the name of the job which automatically gets created from Jenkinsfile. By default it takes the name of the git branch where it finds the JenkinsFile. Thanks and Regards Vishad Alekh -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/gkI8CFySI4c/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/64445e87-6f3c-4aaf-881e-6a2cfe6c6dcd%40googlegroups.com <https://groups.google.com/d/msgid/jenkinsci-users/64445e87-6f3c-4aaf-881e-6a2cfe6c6dcd%40googlegroups.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20161003060202.5910610.29917.25542%40gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/20161003060202.5910610.29917.25542%40gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/gkI8CFySI4c/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFFQucWQ_FrLGzUAOwbbFYSY2amhaNFE-Q9F9UuENrT1A%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFFQucWQ_FrLGzUAOwbbFYSY2amhaNFE-Q9F9UuENrT1A%40mail.gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20161004063337.5910610.91103.25579%40gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/20161004063337.5910610.91103.25579%40gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHQeOGREZXBoqW2Pi8xfTXtOe0AXPaZcT4VUQiED86nDg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
