jenkins-2

I am using Ansible for provision our servers, I installed the Jenkins 2.0 but it is becomeing with a startup configuration when I open the web UI. How can I do it with Ansible or shell or jenkins-cli. CentOS 7, Ansible 2.0.1.0. So, Installing Jenkins 2.0 from http://pkg.jenkins-ci.org/redhat-rc/jenkins-2.0-1.1.noarch.rpm rpm. Install java with yum. Service start jenkins. Open 192.168.46.10:8080, which is opening the Jenkins. In Web UI adding the initial admin password. In web UI select and install plugins. In web UI create a new admin user. The 5,6,7 points are all the startup config of the

I am running the following docker image jenkinsci/jenkins:2.0-rc-1 to try out jenkins 2.0, and the "pipeline" view. I can't seem to install node. Here's my pipeline script: node { //tool([name: 'node-5.10.1', type: 'jenkins.plugins.nodejs.tools.NodeJSInstallation']) sh 'echo $(whoami)' sh 'node -v' } The response when this runs is: [ci] Running shell script + whoami + echo jenkins jenkins [Pipeline] sh [ci] Running shell script + node -v /../durable-3b0b1b07/script.sh: 2: /../durable-3b0b1b07/script.sh: node: not found Here's what i've tried: the jenkins NodeJS tool (which works correctly when

I have a Jenkins 2.0 pipeline, with a groovyscript like this: node('nnh561.raijin') { stage 'checkout' build('trunk/checkout') stage 'build' parallel( { build('trunk/build/gfortran') }, { build('trunk/build/ifort') } ) } Each of the individual jobs builds fine, but when I try to run the pipeline, it spits out this error when it hits the parallel step: java.lang.IllegalArgumentException: Expected named arguments but got [org.jenkinsci.plugins.workflow.cps.CpsClosure2@242d0d3a, org.jenkinsci.plugins.workflow.cps.CpsClosure2@9bf6d64] at org.jenkinsci.plugins.workflow.cps.DSL.parseArgs(DSL.java

Is there a better way to run a shell task in a Jenkins 2.0 pipeline and then return the stdout of the command. The only way I can get this to work is to pipe the output of the command to a file and then read the file in to a variable. sh('git config --get remote.origin.url > GIT_URL') def stdout = readFile('GIT_URL').trim() This seems like a really bad way to return the output. I was hoping I could do something like: def stdout = sh('git config --get remote.origin.url').stdout or def exitcode = sh('git config --get remote.origin.url').exitcode Is this possible? philbert Yes as luka5z mentioned

Is there a way to get the current tag ( or null if there is none ) for a job in a Jenkinsfile? The background is that I only want to build some artifacts ( android APKs ) when this commit has a tag. I tried: env.TAG_NAME and binding.variables.get("TAG_NAME") both are always null - even though this ( https://issues.jenkins-ci.org/browse/JENKINS-34520 ) indicates otherwise I'd consider returnStdout rather than writing to a file: sh(returnStdout: true, script: "git tag --sort version:refname | tail -1").trim() All the other answers yield an output in any case even if HEAD is not tagged. The

I am working on a Jenkinsfile for use with Jenkins 2.0. The readMavenPom method is not recognized. Is there some configuration I am missing to make this available? My Jenkinsfile: node { stage 'Checkout' checkout scm env.PATH = "${tool 'maven-3'}/bin:${env.PATH}" stage 'Build' def pom = readMavenPom file: 'pom.xml' echo "${pom}" sh "mvn -DskipTests=true verify" } When run, I get the following error: java.lang.NoSuchMethodError: No such DSL method 'readMavenPom' found among [AWSEBDeployment, archive, bat, build, catchError, checkout, deleteDir, dir, echo, emailext, error, fileExists, git, input

I have just installed Jenkins 2.6 (as a fresh install) but I can't seem to find the Maven installation options. Previously I would just be able to go to Jenkins configuration and in the Maven section there would be an option for MAVEN_HOME and to install Maven automatically. However this doesn't appear to be present for me. I have the Maven integration plugin installed. How can I get these to show? Omri Spector Since Jenkins 2.x you can find all the tool configurations (Maven, Ant, Gradle and even the JDK) under the "Global Tools" entry in Jenkins administration (Manage Jenkins). 来源： https:/

Currently my pipeline fails (red), when a maven-job is unstable (yellow). node { stage 'Unit/SQL-Tests' parallel ( phase1: { build 'Unit-Tests' }, // maven phase2: { build 'SQL-Tests' } // shell ) stage 'Integration-Tests' build 'Integration-Tests' // maven } In this example the job Unit-Test's result is unstable, but is shown as failed in the pipeline. How can I change the jobs/pipeline/jenkins to have the (1) the pipeline step unstable instead of failed and (2) the pipeline's status unstable instead of failed. I tried adding the MAVEN_OPTS parameter -Dmaven.test.failure.ignore=true , but