Re: Interested in building your plugin on ci.jenkins.io?

Can you add https://github.com/jenkinsci/sauce-ondemand-plugin too? I finally got it not eating up a ton of memory On Monday, September 5, 2016 at 4:44:40 PM UTC-7, James Dumay wrote: > > Hi Tyler, > > I'd love for https://github.com/jenkinsci/display-url-api-plugin to be > built on that

Re: Plugin execution on a slave

I ran into this recently. It turns out you can't pass an anonymous implementation of MasterToSlaveFileCallable to `call`. It must be a named class. Mark Adamcin http://adamcin.net/ On Tue, Oct 25, 2016 at 2:29 PM, wrote: > A user has asked me to support running my

Plugin execution on a slave

A user has asked me to support running my plugin on a slave but whatever I try I keep getting an “Unable to serialize” exception. My code is now about as basic as it gets and still failing. Any ideas? I’m running Jenkins 2.19.1 and my plugin has a Jenkins version dependency of

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

Hi Raja, Have a look at these methods for job.lastBuild: - http://javadoc.jenkins-ci.org/hudson/model/Run.html#isInProgress() - http://javadoc.jenkins-ci.org/hudson/model/Run.html#getLogFile() I hope be useful. Best regards, Rachel El martes, 25 de octubre de 2016, 19:19:11 (UTC+2),

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

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

groovy script to get the jenkins jobs failures and there cause

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

[ANN] New project meeting time

Hi everyone, In the past, the project meeting used a PDT/PST reference time (11am), which resulted in two DST-related changes every spring and fall e.g. in Europe -- once when the US changed, once when the EU changed. To make the meeting independent of DST changes, we decided in the last

Re: Best practices for setting up a preconfigured dockerized Jenkins

Hi Petr, You're a legend :-) Your advices worked, comrade. Thanks a million!! I didn't use Job DSL, Jenkins.instance.reload() appeared to be all I needed to make changes effective (project and global address). I put "z_" prefix for the reload script to make sure it's run in the last turn -

Re: Wall Display Plugin > 0.6.30 not available

yes it is extending the old parent which doesn't work anymore if you don't override various settings It is what I wanted to say Here is the PR : https://github.com/jenkinsci/walldisplay-plugin/pull/46 I also created a PR to have the rights to do the release

Re: Wall Display Plugin > 0.6.30 not available

I have a strong preference for option 2. The plugin is based on the plugins POM 1.580 though, so not sure what you mean…? Of course 0.6.33 will need to upload to repo.j.o instead of maven.j.o. > On 25.10.2016, at 12:41, Arnaud Héritier wrote: > > Hi, > > I wanted to

Re: Wall Display Plugin > 0.6.30 not available

ERRATUM 1/ Deploy manually the release 0.6.32 (0.6.31 has no tag) On Tue, Oct 25, 2016 at 12:41 PM, Arnaud Héritier wrote: > Hi, > > I wanted to have access to the recent versions of Wall Display Plugin > but it seems that Pelle had some issues to do them and we have not

Wall Display Plugin > 0.6.30 not available

Hi, I wanted to have access to the recent versions of Wall Display Plugin but it seems that Pelle had some issues to do them and we have not binaries after 0.6.30 https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/jenkinswalldisplay The plugin

Jelly: Access field value from another jelly file.

Hello, I have a config.jelly which includes a main jelly file and also some additional (repeatable) jelly files from an other class. The config-main.jelly has a textbox with the field "enteredValue". Now I'd like to use the value, entered in this textbox in the "templates" config.jelly. This