Declarative pipeline "when" tag is pushed

HI ,All, i followed with page https://wiki.jenkins.io/display/JENKINS/GitHub+Branch+Source+Plugin to enable tag will trigger a new build then the questions comes How can I use "when" in declarative pipeline to do something like deployment when a new tag is pushed to remote repository

Re: Build periodically not working in Jenkins v2.92

> On 19. Dec 2017, at 23:46, arunlakhanpal wrote: > > Please share views/advise on the same to help me fix this. Check the /threadDump URL for timer/trigger related threads being busy, as well as the Jenkins log for errors related to timers/triggers. -- You

Build periodically not working in Jenkins v2.92

Hi there, The build periodically functionality of jenkins in our environment stopped working randomly about a month back (v2.62), after trying multiple reboots, writing jobs again from scratch etc. hacks with no luck at fixing the issue, I decided to upgrade jenkins to 2.92, the upgrade though

Jenkins Deadlock

After upgrading from 2.73.3 to 2.89.2 our jenkins has started to experience deadlock. We use the tikal Multijob plugin to run any number of other jobs that extend a common job template. When the Multijob kicks off, it will spin up as many AWS slaves as it needs to run all of the child jobs

Re: Fwd: Disconnect node / reconnect node programmatically (Groovy)

> > Hi, > >I want to have a script (bash) which can disconnect & reconnect a Jenkins slave connected through JNLP. Please do the needful. Thanks & Regards, Sridevi -- You received this message because you are subscribed to the

Changeset in when

In the declarative pipelines presentation at Jenkins World 2017 they presented a nice feature where you can execute certain pipeline stages based on changesets. You can see the syntax in slide 14:

Re: Docker Plugin - Jenkins doesn't have label....

I updated my docker-plugin to 1.1.2 also. On Tuesday, December 19, 2017 at 10:11:29 AM UTC-6, nicolas de loof wrote: > > JENKINS-48490 is not implemented in jenkins-core but docker-plugin, and > should be fixed in 1.1.2 > > 2017-12-19 16:18 GMT+01:00 Mandy Hubbard >: >

Re: Docker Plugin - Jenkins doesn't have label....

JENKINS-48490 is not implemented in jenkins-core but docker-plugin, and should be fixed in 1.1.2 2017-12-19 16:18 GMT+01:00 Mandy Hubbard : > JENKINS-48490 is fixed in 2.89.1. I upgraded to 2.89.1 and am still > seeing the issue. I plan to open a new defect for this. >

Re: "ERROR: missing workspace" and chaining builds

Note that we're having this problem only since we moved to pipeline. Thanks -Vincent On Tuesday, December 19, 2017 at 4:28:07 PM UTC+1, Vincent Massol wrote: > > > > On Tuesday, December 19, 2017 at 2:10:36 PM UTC+1, Reinhold Füreder wrote: >> >> Hi Vincent, >> >> >> >> does it work most of

Re: "ERROR: missing workspace" and chaining builds

On Tuesday, December 19, 2017 at 2:10:36 PM UTC+1, Reinhold Füreder wrote: > > Hi Vincent, > > > > does it work most of the times? If so, could it be related to > https://issues.jenkins-ci.org/browse/JENKINS-27329 >

Re: Docker Plugin - Jenkins doesn't have label....

JENKINS-48490 is fixed in 2.89.1. I upgraded to 2.89.1 and am still seeing the issue. I plan to open a new defect for this. On Monday, December 11, 2017 at 5:32:05 PM UTC-6, Mandy Hubbard wrote: > > Thanks for the reply, Nicolas. Can't say it is the response I was hoping > for but at least I

RE: Jenkins init.groovy compilation

Thank you very much Reinhold Füreder I will look into reflection, but probably just choose to ignore the errors and they do not end up causing problems anyways. And I will consider filling a bug with Jenkins. [Agility PR Solutions] Jason Grammenos | Operations and

Re: "ERROR: missing workspace" and chaining builds

Could it be that the workspace is deleted once the node() ends and that it happens that some other node() calls happen to run on the same node and that Jenkins would allocate a workspace only once per job? That would be strange though. Thanks -Vincent On Tuesday, December 19, 2017 at 2:01:32

RE: "ERROR: missing workspace" and chaining builds

Hi Vincent, does it work most of the times? If so, could it be related to https://issues.jenkins-ci.org/browse/JENKINS-27329 “WorkspaceCleanupThread may delete workspaces of running jobs”? HTH Reinhold From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf

"ERROR: missing workspace" and chaining builds

Hi guys, I regularly get the following errors in our Jenkins pipeline on XWiki: ERROR: missing workspace /home/hudsonagent/jenkins_root/workspace/ XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA on agent-2-1 [main] Caused by: java.io.IOException:

Alternate workspace with concurrent builds disabled, why?

Hi, I have a matrix project, with the toplevel project tied to master and the individual builds selecting agents by label, plus other axes: - cpu = (arm64, amd64, x86) - build = (debug, release) - compiler = (msvc) where "msvc" is an agent label. The project does no allow concurrent