how to modify/add/delete tool installations on a slave using Groovy?

Hey, atm I am using a Groovy script to configure our different Jenkins masters, including the tool installations, eg: mavenDesc = Jenkins.instance.getDescriptorByName("hudson.tasks.Maven"); if (mavenDesc != null) { MavenInstallation mi = new MavenInstallation("maven3.0.2", "/home/jenkins/apac

https certificate for https://pkg.jenkins-ci.org not valid

Hi, It seems that the https certificate for https://pkg.jenkins-ci.org site is no longer valid. Could check that ? Thanks Guillaume Boucherie -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving e

Run A Script on Delete Project?

Is it possible to run a Bash or Groovy script every time a job is deleted? Need to cleanup MySQL DB and a few other bits when a job is deleted. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving e

Reg:using deploy plugin deploy into ear and war files

Hi friends i am using deploy plugin in jenkins deploying artifacts into Jboss server it s displaying error like this if any body know that solution give to me reply Started by user pavankumar Building remotely on sample

Jenkins copy files to next/current build number

Hello All, How you doing. I have question on copying files to current/next build number after build completion. *Path :* (22 is build number) , /var/lib/jenkins/jobs/workspace/builds/22/robot-plugin Thanks -- You received this message because you are subscribed to the Google Groups

Pass one environment variable to another

Hi All Jenkins users I am new to the jenkins world and trying my hands on to build and release for TIBCO Ear's. So i have this structure in SVN Codebase - Branch - Trunk - Tags - GoldenCopy I have multiple projects in Tag //SVN_LOCATION/

Re: https certificate for https://pkg.jenkins-ci.org not valid

I notified the infra team, they're looking into it. On 15.09.2014, at 11:39, Guillaume Boucherie wrote: > Hi, > > It seems that the https certificate for https://pkg.jenkins-ci.org site is no > longer valid. > Could check that ? > > Thanks > Guillaume Boucherie > > -- > You received this m

Branch checkout strategy with Multiple SCMs plugin

I am using Multiple SCMs 0.3 with Git Plugin 2.2.2. I have multiple repos each with multiple branches. How does the default checkout strategy work if one of the repos haven't had any changes since the last build? Would it just checkout the latest commit in one of the branches specified? Thanks

JUC SF Oct 23, 2014: Early Bird Discounts End This Sunday

Hi All, A friendly reminder to take advantage of the Early Bird prices for JUC SF Oct 23, 2014. Prices will increase after this Sunday Sept 21. Agenda is here Registrations: - Attend in P

Re: Cucumber Test Result Plugin - It does not appear at my window the test results

I have the same problem when using the plugin. It seems to be installed and configured correctly, I ran the job and it finished successfully, but I don't see those "pretty" Cucumber test results. The end of the build log shows: [Cucumber Tests] Parsing results. [Cucumber Tests] parsing cucumber

Upgrade from 1.526 -> current: pitfalls?

Hi all, I¹ve inherited a Jenkins install that (to my naïve eyes) looks pretty straightforward. It is 1.526, few plugins, Centos environment. Going through the Wiki and poking around Google, I¹m not seeing anything indicating much in the way of upgrade pain in going from 1.526 to 1.580, aside from

Re: Upgrade from 1.526 -> current: pitfalls?

If the system has not been upgraded in that long, you should probably consider using the long term support release (LTS) instead of upgrading to the latest tip of development. Mark Waite On Mon, Sep 15, 2014 at 2:59 PM, Jamie Lawrence wrote: > Hi all, > > I¹ve inherited a Jenkins install that (

Re: Upgrade from 1.526 -> current: pitfalls?

> If the system has not been upgraded in that long, you should probably consider > using the long term support release (LTS) instead of upgrading to the latest > tip > of development. Is that because this particular system does not seem to get enough attention, or because there are changes in b

Re: Upgrade from 1.526 -> current: pitfalls?

On Mon, Sep 15, 2014 at 3:08 PM, Jamie Lawrence wrote: > > > If the system has not been upgraded in that long, you should probably > consider > > using the long term support release (LTS) instead of upgrading to the > latest tip > > of development. > > Is that because this particular system

Re: Upgrade from 1.526 -> current: pitfalls?

> I'm not aware of problematic changes in that range. I've preferred to stay on > the LTS version because it gets more testing, has longer time between > updates, and is only constructed after some time of people "test driving" > various of the "cutting edge" versions. Thanks for the explanation.

Re: Upgrade from 1.526 -> current: pitfalls?

Generally, if you prefer rarely updating Jenkins, the LTS would be a better choice. Four major releases per year, with two bugfix releases for each of them. - Jenkins uses Jetty as default container (when running `java -jar jenkins.war`) since 1.535, resulting in possible issues with very large

Re: Upgrade from 1.526 -> current: pitfalls?

On 9/15/14, 2:27 PM, "Daniel Beck" wrote: >Generally, if you prefer rarely updating Jenkins, the LTS would be a >better choice. Four major releases per year, with two bugfix releases for >each of them. [...] Thanks for the information - that¹s a really very handy list. I do appreciate it. -

Expanding Parameters when triggering Jobs

Perhaps just not using the right terms to look for an answer as I'm thinking this isn't crazy unique. So "Job A" triggers "Job B". Job A has a parameter called PROJECT_PATH, whose value = "${WORKSPACE}/project/trunk/". When triggering Job B choosing "Current Build Parameters", It passes it st

Can not display new builds when i set "discard old builds".

Hi all, I set "discard old builds" in my jenkins. It's work, but new builds can not display automatically. I need reload configuration from disk manually. Is there any way can automate display new builds whit discard old builds? Thanks. -- You received this message because you are subscribed

Re: Can not display new builds when i set "discard old builds".

My jenkins version is 1.538 在 2014年9月16日星期二UTC+8上午11时26分54秒，丁建雄写道： > > Hi all, > > I set "discard old builds" in my jenkins. It's work, but new builds can > not display automatically. I need reload configuration from disk manually. > Is there any way can automate display new builds whit discard

Stuck build numbers

I've got a Jenkins job 'ivija-my360' that shows builds #1-#19 in the history sidebar, builds a build #20 every time I try to build it, and then forgets about it immediately. It also says "last stable build" is #24. $ ls -l /var/lib/jenkins/jobs/ivija-my360/ total 28 drwxr-xr-x 26 jenkins jenkins

Re: Jenkins/GitHub integration

On Fri, Sep 12, 2014 at 11:34:44AM -0400, Mike Seda wrote: > Hi All, > I am a Systems Administrator who was recently asked to perform a > Jenkins/GitHub integration. > > The requirements are... > > 1) When a GitHub pull request is made, start a Jenkins build. > 2) Tell GitHub through the APIs tha