Difference between revisions of "Localyzer Jenkins Configure System"
(→Environment Variables) |
|||
| Line 5: | Line 5: | ||
The following are the name value pairs to add: |
The following are the name value pairs to add: |
||
| − | * '''LRM_HOME''' (e.g.: /home/jenkins/lingoport/lrm-server-2. |
+ | * '''LRM_HOME''' (e.g.: /home/jenkins/lingoport/lrm-server-2.2 or /var/lib/jenkins/lingoport/lrm-server-2.2) |
| − | * '''DASHBOARD_HOME''' (e.g.: /home/jenkins/lingoport/dashboard-client-2.0) |
+ | * '''DASHBOARD_HOME''' (e.g.: /home/jenkins/lingoport/dashboard-client-2.0 or /var/lib/jenkins/lingoport/dashboard-client-2.0) |
In addition, if you are using '''TFS''', add the TFS command line executable location to the PATH: |
In addition, if you are using '''TFS''', add the TFS command line executable location to the PATH: |
||
Revision as of 21:02, 6 October 2015
This section assumes that the Jenkins home directory is /home/jenkins. On some systems, the Jenkins home directory is set to /var/lib/jenkins instead. Verify your home directory to follow the instructions below.
Environment Variables
To set the environment variables, select Jenkins and Manage Jenkins on the left. From there, select Configure System. On the configuration page, scroll down to the Global properties section and select Environmental variables.
The following are the name value pairs to add:
- LRM_HOME (e.g.: /home/jenkins/lingoport/lrm-server-2.2 or /var/lib/jenkins/lingoport/lrm-server-2.2)
- DASHBOARD_HOME (e.g.: /home/jenkins/lingoport/dashboard-client-2.0 or /var/lib/jenkins/lingoport/dashboard-client-2.0)
In addition, if you are using TFS, add the TFS command line executable location to the PATH:
- $PATH (e.g.: PATH:/home/jenkins/team_foundation_server/TEE-CLC-12.0.2/ )
Configure Global Security
The minimal configuration would be to setup the configuration with:
- Jenkins' own user database and
- a matrix based security,
with the following privileges:
- anonymous have a set of very few privileges, if any.
- 'authenticated' the ability to run builds, and
- a few administration accounts with all privileges
Note: If you want to continue the configuration using scripts, you need to allow the Job/Read permission on anonymous users, as explained in http://starkandwayne.com/articles/2013/04/12/jenkins-builds-from-cli/.
