Video with visual explanation (from 2022) Since I got a lot of positive feedback to my previously, first visual explanation, I decided to create another video for this question and answer since there are some things which can be visualized better in a graphical video. It visualizes and also updates this answers with the knowledge … Read more
This problem might occur if you are behind corporate proxy and corporation uses its own certificate. Just add “–no-check-certificate” in the command. e.g. wget –no-check-certificate -qO – http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add – It works. If you want to see what is going on, you can use verbose command instead of quiet before adding “–no-check-certificate” … Read more
As mentioned in “Polling must die: triggering Jenkins builds from a git hook”, you can notify Jenkins of a new commit: With the latest Git plugin 1.1.14 (that I just release now), you can now do this more >easily by simply executing the following command: curl http://yourserver/jenkins/git/notifyCommit?url=<URL of the Git repository> This will scan all … 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.
Your understanding is correct, an artifact in the Jenkins sense is the result of a build – the intended output of the build process. A common convention is to put the result of a build into a build, target or bin directory. The Jenkins archiver can use globs (target/*.jar) to easily pick up the right … Read more
I was able to do that by using the “branches to build” parameter: Branch Specifier (blank for default): tags/[tag-name] Replace [tag-name] by the name of your tag.
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
The Declarative model for Jenkins Pipelines has a restricted subset of syntax that it allows in the stage blocks – see the syntax guide for more info. You can bypass that restriction by wrapping your steps in a script { … } block, but as a result, you’ll lose validation of syntax, parameters, etc within … Read more
In the Global security menu: Select this value to display HTML:
There is a way to cleanup workspace in Jenkins. You can clean up the workspace before build or after build. First, install Workspace Cleanup Plugin. To clean up the workspace before build: Under Build Environment, check the box that says Delete workspace before build starts. To clean up the workspace after the build: Under the … Read more