You should make your build commands work correctly when running inside the same node (avoid using locations outside of the workspace).
On Wednesday, May 10, 2017 at 4:52:06 AM UTC-7, Marslo Jiao wrote: > > Is there anyway that I can manage the executor number for the same Jenkins > job (using jenkins 2.0 pipeline as code)? All multiple builds in the same > job will failed due to resource conflict. > > > Here is my situation: > > > - In the slave configuration, the *# of executors *was set as *2:* > > > <https://lh3.googleusercontent.com/-PiwUQGSuEqU/WRL8pFHrvsI/AAAAAAAAAFQ/6tL-IygHg-QPlzku2iWE90ElUyRZxDoHwCLcB/s1600/pipeline-executor-1.png> > > - But lots Jenkins job will be triggered on this node at the same time: > > > <https://lh3.googleusercontent.com/-6LpTgQmbDAo/WRL82er_lFI/AAAAAAAAAFU/KO_P_BEWH74uCbMLngi_hsw-22ML8PThQCLcB/s1600/pipeline.png> > > > The Jenkinsfile is: > node ('ios') { > stage ("Preparation") { > sh ''' > ... ... > ''' > } > stage ("Preparation") { > sh ''' > ... ... > ''' > } > ... > } > > Thanks a lot. > -- 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/b2a7fd65-bed9-4b1f-946b-9d8269d9939a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
