RE: Installer return 3010, and pipeline failed

Hi Charles, I guess you are executing the installer in the pipeline via “sh” step: thus, you will need to catch the exit/return code (instead of output) from “sh” step and script the logic based on the allowed bad exit code; for example: def exitCode = script.sh(returnStatus: true, script:

Installer return 3010, and pipeline failed

In my pipeline, after installation, there is a pending reboot. Installer return 3010 Pipeline failed: ERROR: script returned exit code 3010 How can I tell pipeline to ignore code 3010 and goto next stage? -- You received this message because you are subscribed to the Google Groups "Jenkins

VM does not shut down after job

This is a continuation of an earlier thread, but is unique going forward, so... We are running Jenkins 2.87 controlling many VMware VM's hosted on an ESXi 5.5 server (soon to be 6.5) via vCenter / vSphere 5.5. They are various versions of Windows. (Using Java 1.44 since that is what was

RE: Parameterized Scheduler is not working in the Jenkins

Rishabh, One little quirk I also found is that you must add your parameter names to the job through the “This project is parameterized” option, save the job, then go back into configure and you should then see the “Build periodically with parameters” option, where you can add the run times and

RE: Parameterized Scheduler is not working in the Jenkins

Rishabh, I have this plugin (version 0.5) installed on my Jenkins environment using the latest LTS version of Jenkins (2.73.3), and it has been running under previous versions as well with no problem. Did you restart Jenkins after you installed the plugin? I’ve had issues in the past where

Parameterized Scheduler is not working in the Jenkins

Hellow everyone, See this image i have installed "Parameterized Scheduler" plugin But this plugin is not continued by the jenkins

Jenkins build unstable while loading artifact from repo.maven.org instead of internal Nexus.

Hello, one of my build gets "UNSTABLE" while downloading two artifact from the Arquillian deployment dependencies. For some reason it does not load the dependency from the internal Nexus repository which does contain the required artifacts. This is the message in the logs: Nov 15, 2017

Re: Debian packages

> On 15. Nov 2017, at 08:30, 'Thomas Martitz' via Jenkins Users > wrote: > > the debian package wasn't updated to 2.90. Is that intentional? > Not intentional, the process was hanging. Should be available shortly. -- You received this message because you

Debian packages

Hello, the debian package wasn't updated to 2.90. Is that intentional? Best regards -- 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 it, send an email to

Role Strategy Plugin

Hi all, I have a question about Role Strategy Plugin. We use version 2.6.1. I get answer from this query : curl -X GET -uX: 'http://localhost:8081/role-strategy/strategy/getAllRoles' But when i try to add a new role I get this : curl -X POST -uX: