Jenkins plugin upgrade cycle

[nitin chadha]

Hello,
I am trying to understand the plugin upgrade cycle. I am writing a plugin 
which will configure parameters sent by samson (
https://github.com/zendesk/samson) with jenkins. There would be future 
updates to the information sent by it to jenkins, and I want all this to be 
configured automatically for all the jobs. 
One way is to make changes to plugin and release a new version. But in 
doing so, I want to know if there are some extensions which i can hook into 
to update configuration for all jobs to use new version of this plugin?


Can some one please point me in the right direction ?
--
Best, 
Nitin Chadha

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/37693326-8b29-4df1-b764-bfdc3be639d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins-infra] Scheduled infrastructure maintenance Oct 27 00:00 UTC

[R. Tyler Croy]

I am pleased to report that the maintenance window has completed, and outside
of some Docker annoyances everything went fairly well.


I will continue to keep an eye on services for the next couple hours just in
case, but please continue your regularly scheduled Jenkins hacking :)

- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20161027012225.GO3357%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: Adding a node with Queue.withLock in Jenkins

[Surya Gaddipati]

Stephen, 

I remember you mentioning it a JIRA ( which I can't seem to find now for 
the life of me)  that Cloudbees Jenkins runs some sort of 'deadlock killer' 
on a timer . 

Is my memory serving me right about this? Do you have that in a plugin 
somewhere if so? 

Surya 

On Monday, October 17, 2016 at 9:53:23 AM UTC-5, Surya Gaddipati wrote:
>
> Hi all, 
>
> I am working on  plugin 
>  that 
> creates a single use computer/node whose lifecycle is tied to a single 
> build .  I am currently adding the node like this 
>
> Jenkins.getInstance().addNode(node); 
>
>
> However that method requires multiple Queue locks while doing so. 
>
>
> I believe in my particular case there is no need for queue locking since 
> only a single build can ever be scheduled on the computer via 
> LabelAssignmentAction. 
>
> I wanted to check ,
>
> 1. if that assumption is correct
>
> 2. If the team is open to accepting a patch to jenkins.instance for  a new 
> method which adds a node without the Queue lock. 
>
>
> Thank you.
>
>
> --Surya
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3d00dd3a-15cd-485c-937b-86f99182ecf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: getScm() on AbstractProject vs. Run

[Jesse Glick]

On Wed, Oct 26, 2016 at 6:54 PM, Stephen Connolly
 wrote:
> That's the one you want (it does the lookups for you)

Do not call that directly. Use
`SCMTriggerItem.asSCMTriggerItem(job).getSCMs()` plus a null check.


Anyway for the stated use case

> Compute the warnings in a build and map these warnings to corresponding SCM 
> changes

`getScm()` was not what you wanted to begin with. You want

Run run = …;
@SuppressWarnings("unchecked") List changeSets =
  run.getClass().getMethod("getChangeSets").invoke(run);

which will work equally well on `AbstractBuild` or `WorkflowRun`. A
core interface to abstract the two is pending.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0RezxRsRzJuoAHfNROe1nisrQse%2BHB%3DOEqMnwtn9AW%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: getScm() on AbstractProject vs. Run

[Stephen Connolly]

That's the one you want (it does the lookups for you)

On Wednesday 26 October 2016, Slide  wrote:

> There is also [1]
>
> 1 - https://github.com/jenkinsci/workflow-job-plugin/blob/
> master/src/main/java/org/jenkinsci/plugins/workflow/
> job/WorkflowJob.java#L539
>
> On Wed, Oct 26, 2016 at 3:46 PM Ullrich Hafner  > wrote:
>
>> I see. Would it work if we loop through all these actions? (This implies
>> that we need to know the exact type of these actions, or is there a method
>> to query only SCM actions?)
>>
>> What we are trying to achieve:
>> Compute the warnings in a build and map these warnings to corresponding
>> SCM changes: this enables us to identify new warnings (and the users who
>> committed these new warnings).
>>
>>
>> Am 27.10.2016 um 00:29 schrieb Stephen Connolly <
>> stephen.alan.conno...@gmail.com
>> >:
>>
>> Well part of the issue is that there can be more than one scm.
>>
>> I think each scm used attaches a tracking action... most likely
>> associated with the node that the checkout was performed on
>>
>> On Wednesday 26 October 2016, Ullrich Hafner > > wrote:
>>
>>> Is there an equivalent method for a Run (e.g. a pipeline job) to get the
>>> used SCM?
>>> Method getScm() is available in AbstractProject but not in the parent
>>> class Run.
>>>
>>> Ulli
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/jenkinsci-dev/B1B4B44B-AF8F-4269-A907-65D9AE9A9E21%40gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Sent from my phone
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com
>> 
>> .
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-dev/CA%2BnPnMzOZxs%3DvQfFKNtRMfR0poS%
>> 3DuYBNJPdMQB_zPqxbKWDv2A%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com
>> 
>> .
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-dev/97DC84D6-40CD-4607-8963-0D75DA60940C%40gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com
> 
> .
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAPiUgVdKDwWHOv9aTcmxkOaaHUPZP
> iv7-_8YJZOgv2Nm4VYV9A%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my phone

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyjgb65hiS-ECr0i3mvMtaL8K%2BKfoB4ZrGpGRH4YNspPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: getScm() on AbstractProject vs. Run

[Slide]

There is also [1]

1 -
https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java#L539

On Wed, Oct 26, 2016 at 3:46 PM Ullrich Hafner 
wrote:

> I see. Would it work if we loop through all these actions? (This implies
> that we need to know the exact type of these actions, or is there a method
> to query only SCM actions?)
>
> What we are trying to achieve:
> Compute the warnings in a build and map these warnings to corresponding
> SCM changes: this enables us to identify new warnings (and the users who
> committed these new warnings).
>
>
> Am 27.10.2016 um 00:29 schrieb Stephen Connolly <
> stephen.alan.conno...@gmail.com>:
>
> Well part of the issue is that there can be more than one scm.
>
> I think each scm used attaches a tracking action... most likely associated
> with the node that the checkout was performed on
>
> On Wednesday 26 October 2016, Ullrich Hafner 
> wrote:
>
> Is there an equivalent method for a Run (e.g. a pipeline job) to get the
> used SCM?
> Method getScm() is available in AbstractProject but not in the parent
> class Run.
>
> Ulli
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/B1B4B44B-AF8F-4269-A907-65D9AE9A9E21%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Sent from my phone
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMzOZxs%3DvQfFKNtRMfR0poS%3DuYBNJPdMQB_zPqxbKWDv2A%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/97DC84D6-40CD-4607-8963-0D75DA60940C%40gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdKDwWHOv9aTcmxkOaaHUPZPiv7-_8YJZOgv2Nm4VYV9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: getScm() on AbstractProject vs. Run

[Ullrich Hafner]

I see. Would it work if we loop through all these actions? (This implies that 
we need to know the exact type of these actions, or is there a method to query 
only SCM actions?) 

What we are trying to achieve:
Compute the warnings in a build and map these warnings to corresponding SCM 
changes: this enables us to identify new warnings (and the users who committed 
these new warnings).
 

> Am 27.10.2016 um 00:29 schrieb Stephen Connolly 
> :
> 
> Well part of the issue is that there can be more than one scm.
> 
> I think each scm used attaches a tracking action... most likely associated 
> with the node that the checkout was performed on
> 
> On Wednesday 26 October 2016, Ullrich Hafner  > wrote:
> Is there an equivalent method for a Run (e.g. a pipeline job) to get the used 
> SCM?
> Method getScm() is available in AbstractProject but not in the parent class 
> Run.
> 
> Ulli
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/B1B4B44B-AF8F-4269-A907-65D9AE9A9E21%40gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> Sent from my phone
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMzOZxs%3DvQfFKNtRMfR0poS%3DuYBNJPdMQB_zPqxbKWDv2A%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/97DC84D6-40CD-4607-8963-0D75DA60940C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: getScm() on AbstractProject vs. Run

[Stephen Connolly]

Well part of the issue is that there can be more than one scm.

I think each scm used attaches a tracking action... most likely associated
with the node that the checkout was performed on

On Wednesday 26 October 2016, Ullrich Hafner 
wrote:

> Is there an equivalent method for a Run (e.g. a pipeline job) to get the
> used SCM?
> Method getScm() is available in AbstractProject but not in the parent
> class Run.
>
> Ulli
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com .
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/B1B4B44B-AF8F-4269-A907-65D9AE9A9E21%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my phone

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMzOZxs%3DvQfFKNtRMfR0poS%3DuYBNJPdMQB_zPqxbKWDv2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

getScm() on AbstractProject vs. Run

[Ullrich Hafner]

Is there an equivalent method for a Run (e.g. a pipeline job) to get the used 
SCM? 
Method getScm() is available in AbstractProject but not in the parent class 
Run. 

Ulli

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/B1B4B44B-AF8F-4269-A907-65D9AE9A9E21%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Scheduled infrastructure maintenance Oct 27 00:00 UTC

[R. Tyler Croy]

I am scheduling a maintenance window for later today (17:00 PDT / 00:00 UTC)
for 60 minutes to apply some new kernel patches to the project's
infrastructure.

The ticket to track this work can be found here:



This will be a simple update and reboot so service outages should be minimal. I
will update this thread once everything has been completed.


Cheers
- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20161026171049.GN3357%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: Plugin execution on a slave

[Jesse Glick]

On Tue, Oct 25, 2016 at 8:01 PM, Mark Adamcin  wrote:
> It turns out you can't pass an anonymous
> implementation of MasterToSlaveFileCallable to `call`. It must be a named
> class.

Specifically a *static* nested class (or top-level class). It is the
synthetic `this$0` field or whatever that is unserializable.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr27Coj0_4LFXvXDV6Cbazvmf-adHpNh5hBuf7LLUOUjZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Klocwork Plugin commit access

[Jacob Larfors]

Hello,

myself and a colleague have a pull request for the Klocwork Jenkins plugin 
that has not been responded to. We have tried contacting the owner but 
cannot get hold of him.
Repository: https://github.com/jenkinsci/klocwork-plugin

Requesting commit access to this repository as we actively maintain this 
plugin in a separate repository and currently provide .hpi files for new 
versions with fixes / new features that we would gladly like to merge & 
share with the wider world.

Github account: jlarfors

Thanks for the help!

Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/aa3debf4-685f-4554-b8c5-f7cdebccdf08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: groovy script to get the jenkins jobs failures and there cause

[raja saggam]

any suggestions how to proceed with this task

On Wednesday, October 26, 2016 at 2:55:22 PM UTC+5:30, raja saggam wrote:
>
> Hi Jimilian,
>
> i am trying to get the reason why jenkins jobs failed for example code 
> changes, build steps etc.
>
> Regards,
> raja
>
> On Wednesday, October 26, 2016 at 12:59:18 PM UTC+5:30, Jimilian wrote:
>>
>> Are you trying to implement 
>> https://github.com/jenkinsci/build-failure-analyzer-plugin?
>>
>> On Tuesday, 25 October 2016 19:19:11 UTC+2, raja saggam wrote:
>>>
>>> I have used the below code where i am getting list of failed jobs and 
>>> also the jobs which are currently inprogress
>>>
>>> hudsonInstance = hudson.model.Hudson.instance
>>> allItems = hudsonInstance.items
>>> activeJobs = allItems.findAll{job -> job.isBuildable()}
>>> failedRuns = activeJobs.findAll{job -> job.lastBuild.result == 
>>> hudson.model.Result.FAILURE}
>>> failedRuns.each{run -> println(run.name)}
>>>
>>>
>>> how to skip those jobs which are running  
>>> and the getting the cause of the jobs which are failed
>>>
>>> On Tuesday, October 25, 2016 at 10:42:00 PM UTC+5:30, raja saggam wrote:

 I looking out to write the groovy script to list the failure jenkins 
 jobs and there cause for the failure

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/35900bde-6b3a-4906-ac6a-2fcb4736f752%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: groovy script to get the jenkins jobs failures and there cause

[raja saggam]

Hi Jimilian,

i am trying to get the reason why jenkins jobs failed for example code 
changes, build steps etc.

Regards,
raja

On Wednesday, October 26, 2016 at 12:59:18 PM UTC+5:30, Jimilian wrote:
>
> Are you trying to implement 
> https://github.com/jenkinsci/build-failure-analyzer-plugin?
>
> On Tuesday, 25 October 2016 19:19:11 UTC+2, raja saggam wrote:
>>
>> I have used the below code where i am getting list of failed jobs and 
>> also the jobs which are currently inprogress
>>
>> hudsonInstance = hudson.model.Hudson.instance
>> allItems = hudsonInstance.items
>> activeJobs = allItems.findAll{job -> job.isBuildable()}
>> failedRuns = activeJobs.findAll{job -> job.lastBuild.result == 
>> hudson.model.Result.FAILURE}
>> failedRuns.each{run -> println(run.name)}
>>
>>
>> how to skip those jobs which are running  
>> and the getting the cause of the jobs which are failed
>>
>> On Tuesday, October 25, 2016 at 10:42:00 PM UTC+5:30, raja saggam wrote:
>>>
>>> I looking out to write the groovy script to list the failure jenkins 
>>> jobs and there cause for the failure
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/dad59bcd-2ef4-4137-bdfc-8a8a2c30b377%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Repository access nodejs-plugin

['Nikolas Falco' via Jenkins Developers]

Hi guys any news?

Il giorno lunedì 17 ottobre 2016 18:33:59 UTC+2, Nikolas Falco ha scritto:
>
> Hi, 
>   I've made a PR  28 
> days ago to resolve an issue of nodejs-plugin.
>
> Seems that repository is no more mantained, so I've read these 
>  
> page for rules on how to post a PR and I would ask write grant for user 
> nfalco79  for repo nodejs-plugin 
> 
>
>
> Best Regards
>
> Nikolas Falco
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/aac639cd-b929-49db-988b-906448e59bdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: groovy script to get the jenkins jobs failures and there cause

[Jimilian]

Are you trying to 
implement https://github.com/jenkinsci/build-failure-analyzer-plugin?

On Tuesday, 25 October 2016 19:19:11 UTC+2, raja saggam wrote:
>
> I have used the below code where i am getting list of failed jobs and also 
> the jobs which are currently inprogress
>
> hudsonInstance = hudson.model.Hudson.instance
> allItems = hudsonInstance.items
> activeJobs = allItems.findAll{job -> job.isBuildable()}
> failedRuns = activeJobs.findAll{job -> job.lastBuild.result == 
> hudson.model.Result.FAILURE}
> failedRuns.each{run -> println(run.name)}
>
>
> how to skip those jobs which are running  
> and the getting the cause of the jobs which are failed
>
> On Tuesday, October 25, 2016 at 10:42:00 PM UTC+5:30, raja saggam wrote:
>>
>> I looking out to write the groovy script to list the failure jenkins jobs 
>> and there cause for the failure
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9e5e49cc-3116-4583-bf6a-02c9e246b694%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.