Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can set per-job users (who has access to/can build a particular job).</p> <p>Under "Manage Jenkins" > "Configure System" ></p> <ul> <li>Click on <strong>Enable Security</strong></li> <li>Check <strong>Project-based Matrix Authorization Strategy</strong></li> </ul> <p>However, I do not think there is a "per-build" option for a single job. </p> <p>If you have the same project that you are sharing between teams, you could (and probably should) create two jobs for this project, and have different libraries/scripts be used in each.</p> <p>You could also parametrize the build (On the Job Page, "Configure" > <strong>This build is parametrized</strong>) and supply the library versions, etc via string parameters.</p> <p>You could also use a parameter to be the team's name, and in your build script change libraries based on the parameter:</p> <p>For example, have a parameter called "TEAM", with choices: TEAM_A and TEAM_B, and in your script, have </p> <pre><code>if [ $TEAM == "TEAM_A" ] then ANT_HOME=/opt/ant/libA else ANT_HOME=/opt/ant/libB fi </code></pre> <p><strong>======================================================================</strong></p> <p>Have you considered sourcing your settings? In Linux, you could do this by saving your OS settings in a script file (for example paths, etc), and using <code>source /path/to/settings/file</code>, in Windows it would be <code>call /path/to/settings/batch/file</code>.</p> <p>Can you give examples of OS level settings that you would require and per-build user for?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload