Re: Jenkins 2.0 pipeline as code executor question

I think this is the Jenkins Slave issue. And create a issue at: https://issues.jenkins-ci.org/browse/JENKINS-44267 -- 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

Re: Jenkins 2.0 pipeline as code executor question

t; date > /Users/devops/hello.txt' >sh 'npm install -g foo' > } > > > On Wednesday, May 10, 2017 at 8:40:31 PM UTC-7, Marslo Jiao wrote: >> >> What "avoid using locations outside of the workspace" means? >> >> On Thursday, M

Re: Jenkins 2.0 pipeline as code executor question

Hi Björn, This job is about to build an app based on iOS. During the app building. The conflict, for example is, there's a key need to be installed like: security unlock-keychain -p xxx.keychain security import -k xxx.keychain -t priv -f pkcs12 -A -P < LOGIN_PWD> The key will be unlock once an

Re: Jenkins 2.0 pipeline as code executor question

> 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. &g

Re: Jenkins 2.0 pipeline as code executor question

The Jenkinsfile is node ('ios') { stage ("Preparation") { // repo checkout } stage ("Build") { // npm install // npm run my-command } ... } Build Trigger is:

Jenkins 2.0 pipeline as code executor question

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:* <