Re: declarative pipeline - gradle build tool not working

[Indra Gunawan (ingunawa)]

What is “GRADLE_LATEST”?
You need to go Jenkins and install Gradle Plugin then add  Gradle to the tool 
in Jenkins 2.x:  Go to Manage Jenkins -> Global Tool Configuration -> Gradle 
Installation;  In Jenkins 1.x: Go to Manage Jenkins -> Configure System -> 
Gradle

For a Gradle version you install you specify a label and then use that label 
ex. “Gradle-2.14” in the declarative pipeline

tools {
gradle “Gradle-2.14”
…

}

On the node/agent, you better make sure the Gradle you install also available 
in the same installation location you just did above.


-Indra

From:  on behalf of Bill Dennis 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Wednesday, February 15, 2017 at 6:40 PM
To: Jenkins Users 
Subject: declarative pipeline - gradle build tool not working

Hi -

I'm looking to use gradle to run tests in declarative pipeline jobs.

Looking at docs here under tools I should be able to spec a gradle tool in the 
tools section:
https://jenkins.io/doc/book/pipeline/syntax/#declarative-steps

So I created a job like this:

pipeline {
agent any
tools {
gradle "GRADLE_LATEST"
}
stages {
stage('Gradle') {
steps {
sh 'gradle --version'
}
}
}
}

But I am getting an error that gradle is not a valid tool type:


org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

WorkflowScript: 4: Invalid tool type "gradle". Valid tool types: [ant, 
hudson.tasks.Ant$AntInstallation, 
com.cloudbees.jenkins.plugins.customtools.CustomTool, 
org.jenkinsci.plugins.docker.commons.tools.DockerTool, git, 
hudson.plugins.git.GitTool, hudson.plugins.gradle.GradleInstallation, 
hudson.plugins.groovy.GroovyInstallation, jdk, hudson.model.JDK, jgit, 
org.jenkinsci.plugins.gitclient.JGitTool, jgitapache, 
org.jenkinsci.plugins.gitclient.JGitApacheTool, maven, 
hudson.tasks.Maven$MavenInstallation, 
hudson.plugins.mercurial.MercurialInstallation] @ line 4, column 9.

   gradle "GRADLE_LATEST"

   ^



1 error



This is on Jenkins Enterprise 2.32.1.1 with version 1.0 of the Pipeline Model 
plugins installed and with the gradle tool plugin installed and configured.



Has anyone got gradle to work with declarative pipeline?



I think I had it working with scripted pipeline sytax but I prefer this tools 
section.



Thanks for any help,

Bill
--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e5506ea0-e080-47b3-b885-cba24454ea61%40googlegroups.com.
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3296514F-78FE-4B4A-8FA7-0BF3FFB714FF%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to trigger remote parameterized build (Found 403 error)

[Sagar Khalasi]

Hi, 

I have found solution but using different plugin and some more 
configuration. 

https://wiki.jenkins-ci.org/display/JENKINS/SiteMonitor+Plugin

*Install above plugin in Jenkins 1.*

*Here I have convert my remote Jenkins (Jenkins 2) machine to public IP. I 
can use it as website or server.*

*Here are some configuration in Jenkins 2 *



As per given above URL , create one URL (Jenkins URL) like below 

http://*.*.*.*:8090/job/remoteTriggerJob/buildWithParameters?token=abcToken=remoteTriggerJob=0
 


Set 200 or 201 status code for response. 

*Note : above URL is customized as per my configuration. Change as per your 
configuration.*


On Wednesday, February 15, 2017 at 8:06:43 PM UTC+5:30, Sri Sayee Shyla 
Hari Laguduva Dhuvaraganath wrote:
>
> Did you find the solution to this issue? I am currently facing it and I am 
> unable to trigger the build
>
> Kindly share your solution with me, if you have found one. Thanks.
>
> On Thursday, December 15, 2016 at 10:50:29 AM UTC, Sagar Khalasi wrote:
>>
>> Yes Found same issue after disable all type security.  So is there any 
>> other way to trigger remote job?
>>
>> On Thursday, December 15, 2016 at 3:43:17 PM UTC+5:30, Sagar Khalasi 
>> wrote:
>>>
>>> Hi all,
>>>
>>> I am trying to follow 
>>> https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin
>>>  
>>> this plugin. 
>>> 
>>>
>>> I have configure it as given. But still found issues like below.
>>>
>>> 1. Server returned HTTP response code: 403 for URL: 
>>> http://192.168.16.138:8090/job/remoteTriggerJob/buildWithParameters?Name=remoteTriggerJob=0
>>>
>>>
>>> 2. Click on above link found this error
>>>
>>> You must use POST method to trigger builds. (From scripts you may 
>>> instead pass a per-project authentication token, or authenticate with your 
>>> API token.) If you see this page, it may be because a plugin offered a GET 
>>> link; file a bug report for that plugin.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> While click on Proceed link , Found build get triggers.
>>>
>>> Please resolve my issue.
>>>
>>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/73c4d881-344c-4391-a81f-510d6fb03074%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

declarative pipeline - gradle build tool not working

[Bill Dennis]

Hi -

I'm looking to use gradle to run tests in declarative pipeline jobs.

Looking at docs here under tools I should be able to spec a gradle tool in 
the tools section:
https://jenkins.io/doc/book/pipeline/syntax/#declarative-steps

So I created a job like this:

pipeline {
agent any
tools {
gradle "GRADLE_LATEST"
}
stages {
stage('Gradle') {
steps {
sh 'gradle --version'
}
}
}
}

But I am getting an error that gradle is not a valid tool type:

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 4: Invalid tool type "gradle". Valid tool types: [ant, 
hudson.tasks.Ant$AntInstallation, 
com.cloudbees.jenkins.plugins.customtools.CustomTool, 
org.jenkinsci.plugins.docker.commons.tools.DockerTool, git, 
hudson.plugins.git.GitTool, hudson.plugins.gradle.GradleInstallation, 
hudson.plugins.groovy.GroovyInstallation, jdk, hudson.model.JDK, jgit, 
org.jenkinsci.plugins.gitclient.JGitTool, jgitapache, 
org.jenkinsci.plugins.gitclient.JGitApacheTool, maven, 
hudson.tasks.Maven$MavenInstallation, 
hudson.plugins.mercurial.MercurialInstallation] @ line 4, column 9.
   gradle "GRADLE_LATEST"
   ^

1 error


This is on Jenkins Enterprise 2.32.1.1 with version 1.0 of the Pipeline Model 
plugins installed and with the gradle tool plugin installed and configured.


Has anyone got gradle to work with declarative pipeline?


I think I had it working with scripted pipeline sytax but I prefer this tools 
section.


Thanks for any help,

Bill

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e5506ea0-e080-47b3-b885-cba24454ea61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: environment variables not getting set

[Sharan Basappa]

Mark,

I think you are referring to point 9 of the article. But that's not I am 
looking for.
We already have environment variables in our .bashrc/.cshrc and there are a 
quite few of them.
So, ideally, we would like to re-use these instead of adding all these 
variables in Jenkins or in my pipeline code.
So, something to leverage existing set-up scripts would be an effective 
approach.

On Thursday, 16 February 2017 01:11:25 UTC+5:30, Mark Waite wrote:

> Refer to item 9 at 
> https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin
>  .
>
> Mark Waite
>
> On Wed, Feb 15, 2017 at 10:59 AM Sharan Basappa  > wrote:
>
>> In my pipeline script, I am running another script that compiles and runs 
>> tests.
>> The script runs some jobs on sungrid. When the build is run, I see that 
>> qrsh (which is the command to launch job on sungrid) was not found.
>> I went back and executed env to check the path and as expected the path 
>> to sungrid was not set.
>>
>> The first thing I did was to go back and add proper path to sungrid in 
>> .bashrc file of Jenkins user.
>> That did not solve the issue as expected, as Jenkins will not run under 
>> bash.
>> Then I created a new file to set proper path and then gave the path in 
>> Jenkins build (using prepare environment I guess ... I don't remember as I 
>> don't have access to Jenkins currently). But this did not help either.
>>
>> I need some help ...
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/3a032339-9981-41e0-ad07-5d3cd2285ea8%40googlegroups.com
>>  
>> 
>> .
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/140c8bce-26df-4f80-a20f-c6ce1ea019c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reset build ID

[Daniel Beck]

> On 15.02.2017, at 21:51, tarocara...@gmail.com wrote:
> 
> Is it possible to reset the build ID? I believe there's a plugin to increase 
> the build ID, but not to reset it to a lower number. It might be a useful 
> feature to be reset it when starting a new release of a product. 

Build numbers must be increasing. So, unless you delete all previous builds, or 
create a new project, '1' is not a valid choice for next build number.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/DFAEE342-7ABF-410B-BEF7-5499F44664BD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Parallel in Declarative Pipeline

['pbeatty' via Jenkins Users]

I can point you to this link on Jenkins.io that describes the declarative 
style and scripting style for Jenkinsfile pipeline.
https://jenkins.io/doc/book/pipeline/jenkinsfile/

On Wednesday, February 15, 2017 at 3:53:58 PM UTC-5, taroc...@gmail.com 
wrote:
>
> What's declarative syntax?
>
> On Wednesday, February 15, 2017 at 11:48:22 AM UTC-8, pbeatty wrote:
>>
>> Is "parallel" valid to use in declarative Jenkinfile syntax or is it only 
>> availabl Scripting syntax?
>>
>> Pat
>>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1f2d7a1c-73e3-495e-abf3-a4877d4bcf4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Parallel in Declarative Pipeline

[tarocaravan]

What's declarative syntax?

On Wednesday, February 15, 2017 at 11:48:22 AM UTC-8, pbeatty wrote:
>
> Is "parallel" valid to use in declarative Jenkinfile syntax or is it only 
> availabl Scripting syntax?
>
> Pat
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ee557cf4-7bb9-4fbd-85d9-38653cffeed2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reset build ID

[Richard Ginga]

Nope, can not reset the build number. it is too ingrained into Jenkins


On Wed, Feb 15, 2017 at 3:51 PM,  wrote:

> Is it possible to reset the build ID? I believe there's a plugin to
> increase the build ID, but not to reset it to a lower number. It might be a
> useful feature to be reset it when starting a new release of a product.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/beef2daf-731e-4f12-a597-54ec63b641fa%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaVisfwTB%3DdaOkzN4FagKKkb6XqNOyB-XXwx670MntyJPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reset build ID

[tarocaravan]

Is it possible to reset the build ID? I believe there's a plugin to 
increase the build ID, but not to reset it to a lower number. It might be a 
useful feature to be reset it when starting a new release of a product. 

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/beef2daf-731e-4f12-a597-54ec63b641fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Using agent dockerfile AND label in a declarative pipeline

[Damien Coraboeuf]

Hi,

I'm starting to migrate some projects to the declarative pipeline model. In 
particular, we want to build on an agent designated by the "docker" label 
(which runs a Docker daemon) and then, I want to build inside a Docker 
container described by my Dockerfile.

Doing this:

pipeline {
   agent {
 label "docker"
 dockerfile true
   }
}

This generates an error:

Only one agent type is allowed per agent section


Now, what should be the best approach to solve this, I think, common 
pattern?

I will try using agent+label, and then using docker+build+inside in steps, 
but would not it more elegant to allow to use both a label and a Dockerfile 
in the agent declaration?

Thanks you for any feedback,
Damien.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c3f4d258-9b63-4744-9b50-47da546bcdb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Parallel in Declarative Pipeline

['pbeatty' via Jenkins Users]

Is "parallel" valid to use in declarative Jenkinfile syntax or is it only 
availabl Scripting syntax?

Pat

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f06f7941-357e-4e69-a1f7-9f6777b166ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: environment variables not getting set

[Mark Waite]

Refer to item 9 at
https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin
 .

Mark Waite

On Wed, Feb 15, 2017 at 10:59 AM Sharan Basappa 
wrote:

> In my pipeline script, I am running another script that compiles and runs
> tests.
> The script runs some jobs on sungrid. When the build is run, I see that
> qrsh (which is the command to launch job on sungrid) was not found.
> I went back and executed env to check the path and as expected the path to
> sungrid was not set.
>
> The first thing I did was to go back and add proper path to sungrid in
> .bashrc file of Jenkins user.
> That did not solve the issue as expected, as Jenkins will not run under
> bash.
> Then I created a new file to set proper path and then gave the path in
> Jenkins build (using prepare environment I guess ... I don't remember as I
> don't have access to Jenkins currently). But this did not help either.
>
> I need some help ...
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/3a032339-9981-41e0-ad07-5d3cd2285ea8%40googlegroups.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF3o4i1XdaUdyuRm8S5UXjeCw7YgA5OGkz1xZ%2BLLeNLZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

environment variables not getting set

[Sharan Basappa]

In my pipeline script, I am running another script that compiles and runs 
tests.
The script runs some jobs on sungrid. When the build is run, I see that 
qrsh (which is the command to launch job on sungrid) was not found.
I went back and executed env to check the path and as expected the path to 
sungrid was not set.

The first thing I did was to go back and add proper path to sungrid in 
.bashrc file of Jenkins user.
That did not solve the issue as expected, as Jenkins will not run under 
bash.
Then I created a new file to set proper path and then gave the path in 
Jenkins build (using prepare environment I guess ... I don't remember as I 
don't have access to Jenkins currently). But this did not help either.

I need some help ...

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3a032339-9981-41e0-ad07-5d3cd2285ea8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Groovy Script to Skip Installation of Plugins and Enable Slave

[Indra Gunawan (ingunawa)]

Add option ‘-Djenkins.install.runSetupWizard=false’ to the JAVA_ARGS for 
Jenkins start-up.


From:  on behalf of Vikas Kumar 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Wednesday, February 15, 2017 at 1:38 AM
To: Jenkins Users 
Subject: Groovy Script to Skip Installation of Plugins and Enable Slave

Hello Everyone,

I am trying to automate initialization of Jenkins Docker container and looking 
to automate two parts.



  *   Ignore this part to select plugins. I don't need this as I am installing 
required plugins at the build time


[https://lh3.googleusercontent.com/-gGElyXPcp8o/WKQgILL71mI/BSc/PR1zR3zjGkYlpkSvJZH0Nkpi4nxfdpmBQCLcB/s400/2017-02-15_19-28-17.png]

















  *   Enable Slave -> Master Access Control (listed under Configure System). 
This has been answered 
here
 but is not working for Jenkins v2.32.2 (latest as on date).
[https://lh3.googleusercontent.com/-1RlmxRmxhaw/WKQgsUfFKuI/BSk/22YPsyXPcpAB7GgwYkVSbIaTmEEtXXZFwCLcB/s400/2017-02-15_19-53-00.png]










Thanks,
Vikas
--
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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/76513c7b-3a9c-4acb-b1fb-3375ce033ef9%40googlegroups.com.
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4B065405-A9DA-42FB-9E03-4E7E5BD08167%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Thanks again... 

it is hurting, thou:)

On Wednesday, February 15, 2017 at 2:24:56 PM UTC+1, Daniel Beck wrote:
>
>
> > On 15.02.2017, at 14:21, christian polzer  > wrote: 
> > 
> > Should i report that with lts version and version of all plugins?? 
>
> You're overriding PATH in an unsupported way. See JENKINS-41339 for 
> solutions. 
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f54a26e9-42d3-41f0-9541-ef1025a47462%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I add builds to the queue a little at a time?

[Chris Overend]

Thank you for your insights.
This reinforces my thoughts after 
reading https://jenkins.io/blog/2016/11/21/gc-tuning/

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fd7b3d25-7206-4750-925a-0efefca9716d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I add builds to the queue a little at a time?

[Baptiste Mathus]

Hello,

The JVM has cool standard features that help you at least know what the
hell it's doing. IMO that's the first thing to do before acting.
You also for instance want to know if really your system is overloaded or
not before possibly growing it, and risking a stab in the dark.

Basically start with vmstat. Especially look for system consistently
swapping. Having a swapping/thrashing jvm/system is indeed going to be very
sluggish.

Then you may want to look at thread dumps and possibly heap dump depending
on some factors.

If you don't feel like you can do that, with my corp cap on, be aware that
some companies like mine do offer professional support for Jenkins. With
your apparent load, it would probably not seem wasteful to be backed by
Jenkins experts.

HTH

Le 3 févr. 2017 3:22 PM, "Chris Overend"  a
écrit :

> I am beginning the process of changing to pipelines.
> We currently use flows to run thousands of jobs(builds).
>
> Say we have 6000 builds to run on 100 Windows virtual machines and 6000
> builds to run on 100 Linux virtual machines.
> To reduce available virtual machines with no jobs to run we try to keep
> the queue as full as possible.
> Each job takes between 1 - 20 min to execute.
>
> I need a way to not over load Jenkins.
> With our current workflow we have to restart Jenkins every couple of days
> as it becomes sluggish (we just purchased and are using a new server).
> We have not determined if Flows with Flows is a contributing factor but
> are beginning testing with Pipelines next week.
>
> We believe the number of jobs in the queue is the cause of our problems,
> but we have not found a better solution than having that many jobs.
>
> My thought was to try and trickle jobs to the queue. I would like to add a
> new job to the queue only if it drops below say 1000.
>
> I am open to other suggestions.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/ca93b1a3-bf6c-4a0d-b41e-60ebf1d2d36d%40googlegroups.
> com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7LnBYNMrtnNR4wLNOuuOA0OSfg84gxW_%2B0-S9%3DjbX6%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Delete workspace for only failed part of the matrix

[Romaric Crailox]

Hello,

I have a Jenkins jobs use for compilation. 
I have 2 axis : PLATFORM and MODE. PLATFORM can take x86 or crosscompile 
value. MODE can take debug or notdebug value.

I have "Delete workspace before build starts" option checked, and "Rerun 
build only for failed parts on the matrix" option of "Retry build after 
failure" plugin checked.
My problem is that if, for exemple, MODE debug on x86 PLATFORM failed, 
Jenkins rerun this part of matrix but delete all workspace at the begining 
of this new rerun. At the end, I have a workspace with only MODE debug on 
x86 PLATFORM that is compiled. Other part of matrix are not compile.


I can't "Delete workspace before build starts" in "Post Build Action" 
instead of "Delete workspace before build starts" because I need a compiled 
project to achieve some test, analysis later.
I would like to keep the principle of cleaning my workspace before build 
because, in my opinion, it permit to supress side effect of some old file 
or folder remaining of an old compilation or test.


Do you have, please, some ideas ?


Best Regards

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b293ae53-78a1-4b0b-9d2f-0b9ef98ae4a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to trigger remote parameterized build (Found 403 error)

[Sri Sayee Shyla Hari Laguduva Dhuvaraganath]

Did you find the solution to this issue? I am currently facing it and I am 
unable to trigger the build

Kindly share your solution with me, if you have found one. Thanks.

On Thursday, December 15, 2016 at 10:50:29 AM UTC, Sagar Khalasi wrote:
>
> Yes Found same issue after disable all type security.  So is there any 
> other way to trigger remote job?
>
> On Thursday, December 15, 2016 at 3:43:17 PM UTC+5:30, Sagar Khalasi wrote:
>>
>> Hi all,
>>
>> I am trying to follow 
>> https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin
>>  
>> this plugin. 
>> 
>>
>> I have configure it as given. But still found issues like below.
>>
>> 1. Server returned HTTP response code: 403 for URL: 
>> http://192.168.16.138:8090/job/remoteTriggerJob/buildWithParameters?Name=remoteTriggerJob=0
>>
>>
>> 2. Click on above link found this error
>>
>> You must use POST method to trigger builds. (From scripts you may instead 
>> pass a per-project authentication token, or authenticate with your API 
>> token.) If you see this page, it may be because a plugin offered a GET 
>> link; file a bug report for that plugin.
>>
>>
>>
>>
>>
>>
>>
>>
>> While click on Proceed link , Found build get triggers.
>>
>> Please resolve my issue.
>>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5e782ea5-04b1-4517-a096-4c38da5b96a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins -> Dockerfile -> Nexus Docker repository, how to do it?

[Jae Gangemi]

if you are just using docker commands you can just push the container yourself 
from a shell build step.

if you have a java project and are using maven, the fabric8 docker plugin is 
excellent.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ca9a386d-baf0-4b4a-9a00-3df7e5eae67a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[Daniel Beck]

> On 15.02.2017, at 14:21, christian polzer  wrote:
> 
> Should i report that with lts version and version of all plugins??

You're overriding PATH in an unsupported way. See JENKINS-41339 for solutions.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/570CE1CF-B086-47C0-9EFC-A41A8128778D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Ok.

updating the plugins did enable the new declarative poipeline, but disabled 
usage of everything path related.. shell "sh"  steps:

Running shell script
nohup: failed to run command ‘sh’: No such file or directory


Should i report that with lts version and version of all plugins??



On Tuesday, February 14, 2017 at 1:14:26 PM UTC+1, Daniel Beck wrote:
>
>
> > On 14.02.2017, at 11:59, christian polzer  > wrote: 
> > 
> > Would it be possible to somehow track the version the documentation is 
> written for? :) 
>
> You can assume latest LTS or newer, with plugins up to date, as these are 
> the only releases we consider to be supported. (I think rtyler has plans to 
> improve this, but I doubt that'll be available soon.) 
>
> Running anything older is frequently a terrible idea anyway, see 
> https://jenkins.io/security/advisories/ 
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/628b08a6-708f-44b6-b83b-4136970941d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Groovy Script to Skip Installation of Plugins and Enable Slave

[Vikas Kumar]

All,

This stands solved now.

To ignore the plugins, just use this

echo ${JENKINS_VERSION} > 
/usr/share/jenkins/ref/jenkins.install.UpgradeWizard.state
echo ${JENKINS_VERSION} > 
/usr/share/jenkins/ref/jenkins.install.InstallUtil.lastExecVersion

and for the enabling slave, the answer here 

 
is good, all one needs is to import the package *import 
jenkins.security.s2m.**

Hope this helps someone.

Cheers,
Vikas

On Wednesday, 15 February 2017 20:38:04 UTC+11, Vikas Kumar wrote:
>
> Hello Everyone,
>
> I am trying to automate initialization of Jenkins Docker container and 
> looking to automate two parts.
>
>
>- Ignore this part to select plugins. I don't need this as I am 
>installing required plugins at the build time
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>- Enable Slave -> Master Access Control (listed under Configure 
>System). This has been answered here 
>
> 
>  
>but is not working for Jenkins v2.32.2 (latest as on date).
>
>
> 
>
>
>
>
>
>
>
>
>
>
> Thanks,
> Vikas
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b38aca98-57c6-4441-8ca2-1b5466582fa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Groovy Script to Skip Installation of Plugins and Enable Slave

[Vikas Kumar]

Hello Everyone,

I am trying to automate initialization of Jenkins Docker container and 
looking to automate two parts.


   - Ignore this part to select plugins. I don't need this as I am 
   installing required plugins at the build time




















   - Enable Slave -> Master Access Control (listed under Configure System). 
This 
   has been answered here 
   

 
   but is not working for Jenkins v2.32.2 (latest as on date).












Thanks,
Vikas

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/76513c7b-3a9c-4acb-b1fb-3375ce033ef9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mercurial webhooks triggering and modules

[mba]

Hi all,

I have a structure of jobs which has a few general jobs, and a lot of 
component jobs. The source for all of them are in the same mercurial repo. 
I want to use webhooks from mercurial as triggers, and then the modules 
part of mercurial checkout to only run the relevant jobs. However it 
appears that all jobs are run on a webhook trigger no matter the module 
path. Is this as expected, and do anyone have an idea for how I can produce 
the setup want. I create the jobs as pipelineJob using jobDSL and seedjob 
to create them.

My job structure is something like this
ProjectName (folder)
   -> Branch name (folder)
   -> general 1 (job)
   -> general 2 (job)
   -> comp1 (job)
   -> comp2 (job)
   ->
   ->
   -> comp30

When I checkout in "general 1" I use this code:
checkout([$class: 'MercurialSCM',
  revision: 'default',
  poll: true,
  credentialsId: 'mercurial-RO',
  source: 'REPO-URL'])

and from comp1 I use this, where the modules path is included

checkout([$class: 'MercurialSCM', 
  revision: 'default', 
  poll: true,
  credentialsId: 'mercurial-RO', 
  modules: 'FrameworkComponents\\SystemServices', 
  source: 'REPO-URL'])

My webhook is based on the example on the plugin page:

[hooks]

commit.jenkins = wget -q -O /dev/null  
JENKINS-URL/mercurial/notifyCommit?url=REPO-URL

incoming.jenkins = wget -q -O /dev/null 
JENKINS-URL/mercurial/notifyCommit?url=REPO-URL


Do any of you have any suggestions? My server is taking some hard hits by 
having to run all 30 jobs, when just one component is changed.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7059420b-61b1-4eca-a21e-15b8e85303f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.