Modern Jenkins versions (since 2.26, October 2016) solved this: it’s just an advanced option for the Execute shell build step! You can just choose and set an arbitrary exit value; if it matches, the build will be unstable. Just pick a value which is unlikely to be launched by a real process in your build.
Since Jenkins 2.129 the API token configuration has changed: You can now have multiple tokens and name them. They can be revoked individually. Log in to Jenkins. Click you name (upper-right corner). Click Configure (left-side menu). Use “Add new Token” button to generate a new one then name it. You must copy the token when … Read more
Michael, Two things: When Jenkins connects to a computer, it goes to the sh shell, and not the bash shell (at least this is what I have noticed – I may be wrong). So any changes you make to $PATH in your bashrc file are not considered. Also, any changes you make to $PATH in … Read more
The Git plugin has an option (excluded region) to use regexes to determine whether to skip building based on whether files in the commit match the excluded region regex. Unfortunately, the stock Git plugin does not have a “included region” feature at this time (1.15). However, someone posted patches on GitHub that work on Jenkins … Read more
jenkins is a service account, it doesn’t have a shell by design. It is generally accepted that service accounts shouldn’t be able to log in interactively. I didn’t answer this one initially as it’s a duplicate of a question that has been moved to server fault. I should have answered rather than linked to the … 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
Keychains need to be unlocked before they can be used. You can use security unlock-keychain to unlock. You can do that interactively (safer) or by specifying the password on the command line (unsafe), e.g.: security unlock-keychain -p mySecretPassword… Obviously, putting this into a script compromises the security of that keychain, so often people setup an … 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
You can use the error step from the pipeline DSL to fail the current build. error(“Build failed because of this and that..”)
You can overwrite the existing jenkins.war file with the new one and then restart Jenkins. This file is usually located in /usr/share/jenkins. If this is not the case for your system, in Manage Jenkins -> System Information, it will display the path to the .war file under executable-war.