Take a look at this plugin :
https://wiki.jenkins-ci.org/display/JENKINS/Job+Restrictions+Plugin
On 12/10/15, 6:01 AM, "jenkinsci-users@googlegroups.com on behalf of Jeff
Storey" wrote:
>Hi, I am trying to find a way to restrict who can execute jobs on
>slaves in this way:
>Users in a certain l
Starting from 1.625.1:
1.625.1 is the first Jenkins LTS release that requires Java 7 to run. If
you're using the Maven Project type, please note that it needs to use a
JDK capable of running Jenkins, i.e. JDK 7 or up. If you configure an
older JDK in a Maven Project, Jenkins will attempt to find a
My two cents,
1) Split your build step in two parts and use the envinject plugin.
Your first step will generate the build name and save to a file.
Then, you can inject that via the envibject plugin and use the set build name
based on that property. Afterwards you can run your script.
2) if you
I would like to set the name of a build programmatically during an "Execute
shell" step. The new name of the build must be calculated based on some
code that runs in the shell.
To clarify, the build name is the value that shows up in the "Build
Executor Status" left sidebar on the main Jenkins
