Re: [blueocean] multi-platform builds with multi-stage completely parallel tracks

As far as I know, *stage* blocks inside parallel tasks are deprecated => see https://github.com/jenkinsci/pipeline-examples/blob/master/docs/BEST_PRACTICES.md#parallelism Have you tried something like : stage ("Setup") { parallel ( 'xenial': { node("xenial") {

Re: Jenkins LTS Release Line: Frequency / Process of Upgrading Jenkins on LTS release schedule

On Mon, Jul 3, 2017 at 3:05 PM Jason LeMauk < jason.lem...@csquaredsystems.com> wrote: > If a renamed copy of the old WAR file exists in $JENKINS_HOME directory, > wouldn’t it just be a matter of changing the previous jenkins war from > jenkins.war.old to jenkins.war, and removing the newly

RE: Jenkins LTS Release Line: Frequency / Process of Upgrading Jenkins on LTS release schedule

If a renamed copy of the old WAR file exists in $JENKINS_HOME directory, wouldn’t it just be a matter of changing the previous jenkins war from jenkins.war.old to jenkins.war, and removing the newly copied Jenkins WAR from the $JENKINS_HOME directory? Isn’t that essentially the undo of the

Re: Jenkins LTS Release Line: Frequency / Process of Upgrading Jenkins on LTS release schedule

Replies inline for clarity. On Mon, Jul 3, 2017 at 2:46 PM Jason LeMauk < jason.lem...@csquaredsystems.com> wrote: > Thank you for the information! As a matter of fact we are using Ubuntu. > > > > As part of the upgrade process, I’ve seen Jenkins administrators do the > following: > > 1.

RE: Jenkins LTS Release Line: Frequency / Process of Upgrading Jenkins on LTS release schedule

Thank you for the information! As a matter of fact we are using Ubuntu. As part of the upgrade process, I’ve seen Jenkins administrators do the following: 1. Stop Jenkins running as a service. 2. Rename Jenkins current WAR file to jenkins.war.old. 3. Copy the new WAR file into

Re: Jenkins LTS Release Line: Frequency / Process of Upgrading Jenkins on LTS release schedule

That is the technique I've used, though I've preferred to simplify the upgrade process by using either Debian or Ubuntu as the host operating system, then installing Jenkins from the "apt" package manager. That simplifies the "upgrade and copy the war" step. It doesn't really remove any of the

RE: Jenkins Distributed Builds: Parameterized Jobs and the Ansible Plugin for Jenkins

Great thank you! That was exactly the information I was looking for. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Richard Ginga Sent: Monday, July 03, 2017 1:39 PM To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins Distributed Builds:

Issue connecting slave on aws EC2 using JNLP4 to on-premise master

Hi all, I've just spin up an EC2 on aws running ubuntu 14 with openjdk 1.8, and i'm trying to connect it to a master hosted within internal network running V 2.46.1 without any clue: i've downloaded the slave.jar to my ec2 the ran the following command: java -jar

Jenkins LTS Release Line: Frequency / Process of Upgrading Jenkins on LTS release schedule

I am currently working to setup a Jenkins server for continuous integration. One area of Jenkins maintenance I am looking at is Jenkins upgrades. As gaining access to new Jenkins features is less important to our setup than receiving important bug fixes and general system stability, I am

Re: Extend pipeline project congfiguration page

> On 3. Jul 2017, at 11:29, David Wilhelm wrote: > > I would like to "simply" add an entry to the per project configuration page > where i can enable my pluign. I'm having trouble finding a way to do that > with multibranch pipeline, i just managed to do that with an

Re: Jenkins supported branch

> On 3. Jul 2017, at 16:32, Paolo Franchini wrote: > > should I do a fresh new installation or is there another way? > You should be able to upgrade. As always, backups are strongly advisable, as is a staging system if you can't deal with some downtime.

Re: Parameterized option in multibranch pipeline job

Okay, so I have to run the first build without parameter. Is there any option to trigger the build without parameter at branch initialization alone? I have set suppress automatic scm trigger in my multibranch pipeline settings for all branches. So it doesn't trigger the build for branch creation

Re: Jenkins Distributed Builds: Parameterized Jobs and the Ansible Plugin for Jenkins

Jason, all parameters are available in the environment of any slave/agent just like they were available when built on the master. as far as ansible and python, I would say you would need to install them on any build machine. On Mon, Jul 3, 2017 at 11:26 AM, Jason LeMauk <

Re: Parameterized option in multibranch pipeline job

Thanks for the reply. I know, I already configured the parameters via properties of jenkinsfile. The problem is, its not get parameterized for the very first build. I suppress all branch scm trigger and I am manually triggering the builds from webhook, so I can't pass the first build with

Restart Jenkins when upgraded by Ubuntu unattended-upgrades

Hi, I have added the Jenkins PPA to the ubuntu unattended-upgrades system so that when a new LTS version is available, Jenkins is automatically upgraded. However, as far as I can tell, this does not restart Jenkins. Ideally, Jenkins would wait to finish any existing jobs, then restart

Jenkins Distributed Builds: Parameterized Jobs and the Ansible Plugin for Jenkins

I currently have a parameterized build setup on my Jenkins master. As these parameters are accessible as environment variables, I'm using them in an ansible script via the ansible plugin. We also have a distributed build architecture in place. With a distributed build system, if this project

Re: Jenkins supported branch

Thanks Daniel, should I do a fresh new installation or is there another way? cheers, Paolo Il giorno lunedì 3 luglio 2017 12:15:23 UTC+1, Daniel Beck ha scritto: > > > > On 3. Jul 2017, at 11:53, Paolo Franchini > wrote: > > > > is 1.651.1 a supported branch with

Re: Add entry to Multibranch Pipeline Configuration

BranchProperty On 3 July 2017 at 10:47, David W wrote: > Hi, > > I'm using feature branches and sonarqube code scanning with a jenkins > multibranch pipeline job. > > Bachground: > Jenkins creates a new job for every new branch, sonarqube scanner notifies > sonarqube and

Add entry to Multibranch Pipeline Configuration

Hi, I'm using feature branches and sonarqube code scanning with a jenkins multibranch pipeline job. Bachground: Jenkins creates a new job for every new branch, sonarqube scanner notifies sonarqube and also creates a new job there. If a brach gets removed, jenkins deletes the corresponding

Extend pipeline project congfiguration page

Hi, I'm building a plugin that listens for job deletions and notifies the Sonarqube Server about that. *Background*: I use feature branches with complete sonarqube scans. Jenkins creates a new job for every branch and the sonarscanner does the same on sonarqube. If a branch gets deleted,

Re: Jenkins supported branch

> On 3. Jul 2017, at 11:53, Paolo Franchini wrote: > > is 1.651.1 a supported branch with security updates? Or is it and end-of-life > one? Couldn't find a page... > It's not, and it hasn't been for over a year. We have two supported release lines, weekly and LTS,

Re: Exception being thrown when trying to create/modify/delete Freestyle Jobs

> On 3. Jul 2017, at 09:48, Baptiste Mathus wrote: > > weird, in your list I can't see Blue Ocean Events, where the > BlueMesssageEnricher class apparently comes from. > The problem is

Re: vSphere Cloud Plugin - does it work ?

Hi John, thanks for sharing your experience with this kind of "issues". Based on what you have sent I am giving up (at least for now) with creating new VMs and follow your steps. How do you use vsphere plugin to reset the slave back ? Are you using VM snapshots ? I would be grateful if you

[blueocean] multi-platform builds with multi-stage completely parallel tracks

Hi, I'm trying to build a pipeline that in principle it sounds like it should be very simple. I basically have a project that I want to build and test for Ubuntu trusty and xenial. So basically I want to run them in separate nodes (which will use Docker). I want to visualize this in blueocean

Jenkins supported branch

Hi, is 1.651.1 a supported branch with security updates? Or is it and end-of-life one? Couldn't find a page... cheers, Paolo -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from

Re: parameterised build which can set multiple values/variables from a choice

Yeah, that's the main disadvantage. But as I mentioned, you can avoid this constraint with tools like Jenkins Pipeline, Job DSL Plugin or Job Builder. 2017-07-03 9:45 GMT+02:00 paul b : > Ok. I get what you're saying but that would mean me creating a job for > each

Re: Fwd: null pointer exception

Periodic reminder: you probably want to move away from the "maven-integration" plugin. 2017-06-29 7:59 GMT+02:00 JanisB : > Hi, > > A downgrade of maven plugin from v 2.16 to v 2.14 solved the same problem > for me on Jenkins 2.66, but this will be a problem if you use

Re: Exception being thrown when trying to create/modify/delete Freestyle Jobs

weird, in your list I can't see Blue Ocean Events, where the BlueMesssageEnricher class apparently comes from. 2017-06-28 22:17 GMT+02:00 Stephen B : > Greetings, > I’m running Jenkins 2.7.3 LTS. I’m trying to create a freestyle project > however, when I go to save,

Re: Why doesn't Jenkins Update Center show certain plugins?

Just for future ref, you generally don't want to do that apart from very specific cases (like for an offline instance). The update manager handles transitive dependencies, which won't be done manually. Hence you take the risk that the instance then refuses to start. The plugin shows up in

Re: parameterised build which can set multiple values/variables from a choice

Ok. I get what you're saying but that would mean me creating a job for each environment(4 environments). Then with the 20 jobs for all the components that would work out to be 80 jobs! Which seems excessive. On Sunday, 2 July 2017 13:49:15 UTC+1, mpapo - Michael Pailloncy wrote: > > Ok. >