You can use the timeout step: timeout(20) { node { sh ‘foo’ } } If you need a different TimeUnit than MINUTES, you can supply the unit argument: timeout(time: 20, unit: ‘SECONDS’) { EDIT Aug 2018: Nowadays with the more common declarative pipelines (easily recognized by the top-level pipeline construct), timeouts can also be specified … Read more
As for declarative syntax, you can use the options block: pipeline { options { buildDiscarder(logRotator(numToKeepStr: ’30’, artifactNumToKeepStr: ’30’)) } … } Parameters for logRotator (from the source code): daysToKeepStr: history is only kept up to this days. numToKeepStr: only this number of build logs are kept. artifactDaysToKeepStr: artifacts are only kept up to this days. … Read more
The exception that you are seeing is due to script security and sandboxing. Basically, by default, when you run a pipeline script, it runs in a sandbox which only allow usage of certain methods and classes. There are ways to whitelist operations, check the link above. The @NonCPS annotation is useful when you have methods … Read more
You can create variables before the pipeline block starts. You can have sh return stdout to assign to these variables. You don’t have the same flexibility to assign to environment variables in the environment stanza. So substitute in python3.5 get_version.py where I have echo 0.0.1 in the script here (and make sure your python script … Read more
If you use a declarative style Pipeline and only want to trigger the build on a specific branch you can do something like this: String cron_string = BRANCH_NAME == “master” ? “@hourly” : “” pipeline { agent none triggers { cron(cron_string) } stages { // do something } } Found on Jenkins Jira
From VS: Open Team Explorer Click Source Control Explorer In the nav bar of the tool window there is a drop down labeled “Workspaces”. Extend it and click on the “Workspaces…” option (yeah, a bit un-intuitive) The “Manage Workspaces” window comes up. Click edit and you can add / remove / edit your workspace From … Read more
Yes, you can. Download the plugin (*.hpi file) and put it in the following directory: <jenkinsHome>/plugins/ Afterwards you will need to restart Jenkins.
Probably use jenkins command line is another option, see https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI create-job: Creates a new job by reading stdin as a configuration XML file. get-job: Dumps the job definition XML to stdout So you can do java -jar jenkins-cli.jar -s http://server get-job myjob > myjob.xml java -jar jenkins-cli.jar -s http://server create-job newmyjob < myjob.xml It works … Read more
I figured it out. In order to save your Jenkins data on other drive you’ll need to do the following: Workspace Root Directory: E:\Jenkins\${ITEM_FULL_NAME}\workspace Build Record Root Directory: E:\Jenkins\${ITEM_FULL_NAME}\builds
Look deeper into the plugin documentations. No need for groovy here. Just make sure Content Type is set to HTML and add the following to the body: ${FILE,path=”my.html”} This will place the my.html content in your email body (location of file is relative to job’s workspace. I use it and it works well. I hope … Read more