Re: RFH: Pipeline support for saltstack build plugin

Hey all, I think I've made a little headway doing a cleanup of the class bits. I've been trying to reconcile Daniel's branch and ui-samples with a more current upstream. Before touching any jelly, I am now able in instantiate the basic class. Now I am currently working at doing a more correct

Jenkins Rest API guide

Wrong mailing list, please ask in the jenkins user mailing list https://jenkins.io/content/mailing-lists/ -- 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

Can't yank a live executor

Wrong mailing list, please ask in the jenkins user mailing list https://jenkins.io/content/mailing-lists/ -- 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

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

Hi Naresh, That's not a Jenkins question, but Groovy question. You're lucky, Christmas time is near ;) Try it with this code from BUILD_STRING declaration (I think it's very readable): ... BUILD_STRING = "Build step 'Execute shell' marked build as failure" failedRuns.each{ item ->

Can't yank a live executor

We have a Jenkins 1.625.3.1 master that shows a so-called live executor. However, we know the job is stuck, as it has been aborted 3 hours ago. I tried doYank() of the executor, but I cannot: Can't yank a live executor Is there a way to recover this thread/executor without restarting

Re: maintainer requests

> On 27.10.2016, at 16:51, Daniel Beck wrote: > > Regarding AWS Cloudformation, I'm still finding out whether it actually is > abandoned. It is: https://groups.google.com/d/msg/jenkinsci-dev/cj0wcKW2cPY/9Vn1wI5lCwAJ So I'd be happy to make you maintainer of any/all of these

Re: Adding a node with Queue.withLock in Jenkins

Thanks Stephen. I appreciate your quick responses. 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

Jenkins Rest API guide

Hi guys! Where can I find a complete reference to the rest api? Maybe examples about how to get the build date. Thanks! -- 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,

Re: maintainer requests

Sure, no problem for me :) Frédéric Camblor BDX.io Leader Restx commiter Jenkins community member & plugin commiter On Thu, Oct 27, 2016 at 4:51 PM, Daniel Beck

Re: Adoption of Amazon ECR Plugin

> On 27.10.2016, at 16:51, Ben McCann wrote: > > Thanks for taking over Daniel! Forwarding the thanks to Ivan who's going to do the actual work -- I just grant permissions ;-) -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: maintainer requests

> On 21.10.2016, at 23:08, Greg Langston wrote: > > https://wiki.jenkins-ci.org/display/JENKINS/NodeJS+Plugin > https://wiki.jenkins-ci.org/display/JENKINS/AWS+Cloudformation+Plugin > https://wiki.jenkins-ci.org/display/JENKINS/Amazon+ECR > > There are a couple of

Re: Adoption of Amazon ECR Plugin

Thanks for taking over Daniel! On Thu, Oct 27, 2016 at 7:44 AM, Daniel Beck wrote: > > > On 27.10.2016, at 15:59, Ivan Fernandez Calvo > wrote: > > > > Daniel, > > > > So now I am the maintainer of Amazon ECR Plugin and SAML Plugin , isn't > it? > > I

Re: Adoption of Amazon ECR Plugin

> On 27.10.2016, at 15:59, Ivan Fernandez Calvo wrote: > > Daniel, > > So now I am the maintainer of Amazon ECR Plugin and SAML Plugin , isn't it? I only added you to Amazon ECR for now. But now I clarified with Dan Tranter, who marked SAML Plugin as up for

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

here is the code for it import hudson.tasks.* import com.cloudbees.hudson.plugins.folder.Folder //Iterate over the each Job activeJobs = hudson.model.Hudson.instance.items.findAll{job -> !(job instanceof Folder) && job.isBuildable()} println("successjobs = " +activeJobs.size()) failedRuns =

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

Hi Rachel, I have used the above function where i'm getting whole console out for last build. can you let me know how to filtered errors from console output using groovy instead of printing the whole console out. Regards, Naresh. On Wednesday, October 26, 2016 at 3:56:35 AM UTC+5:30,

Re: Adoption of Amazon ECR Plugin

Daniel, So now I am the maintainer of Amazon ECR Plugin and SAML Plugin , isn't it? El jueves, 27 de octubre de 2016, 11:26:59 (UTC+2), Daniel Beck escribió: > > > > On 13.10.2016, at 23:06, Ivan Fernandez Calvo > wrote: > > > > Hi guys, > > > > I recently made a PR

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Quick heads-up: we should have more data soon about the share of Java 8 & Java 7: https://github.com/jenkins-infra/infra-statistics/pull/21 In the meantime, any additional review/opinion on that change, and/or the data you think would be interesting to extract from there is welcome. 2016-10-19

Re: getScm() on AbstractProject vs. Run

> >> 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 = >

Re: Adoption of Amazon ECR Plugin

> On 13.10.2016, at 23:06, Ivan Fernandez Calvo wrote: > > Hi guys, > > I recently made a PR to Amazon ECR Plugin and I saw that it is in adoption, > Could be posible to adopt it? currently I do not maintain any plugin but I > made some contributions for few

Re: Adoption of Amazon ECR Plugin

Also I would like to adopt SAML Plugin El jueves, 13 de octubre de 2016, 23:06:24 (UTC+2), Ivan Fernandez Calvo escribió: > > Hi guys, > > I recently made a PR to Amazon ECR >

Re: Adding a node with Queue.withLock in Jenkins

We had a hot fix plugin that would run on a timer and look for a specific deadlock in a specific class with a specific stacktrace and then interrupt a specific thread that we analysed as safe to interrupt. It's not to hard to write one... the hard part is the analysis to identify the criteria for