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 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/64445e87-6f3c-4aaf-881e-6a2cfe6c6dcd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
