Difference between revisions of "Localyzer Jenkins Plugins"
(→Jenkins) |
|||
| Line 1: | Line 1: | ||
| − | ==Jenkins== |
+ | == Install Jenkins== |
Download Jenkins from [https://jenkins-ci.org/ jenkins-ci.org], install it, and run it. Must be <b>version 1.609</b> or later. |
Download Jenkins from [https://jenkins-ci.org/ jenkins-ci.org], install it, and run it. Must be <b>version 1.609</b> or later. |
||
Otherwise, the location of the 'workspace' may vary, causing real problems! Jobs created by this version <b>must</b> have the workspace located under <b>$JENKINS_HOME/jobs/$JOBNAME/workspace</b>. |
Otherwise, the location of the 'workspace' may vary, causing real problems! Jobs created by this version <b>must</b> have the workspace located under <b>$JENKINS_HOME/jobs/$JOBNAME/workspace</b>. |
||
| − | + | == Set up Jenkins Plugins== |
|
You may setup the plugins used by LRM in two ways: |
You may setup the plugins used by LRM in two ways: |
||
* Run the setup script using jenkins-cli.jar at the command line |
* Run the setup script using jenkins-cli.jar at the command line |
||
| Line 11: | Line 11: | ||
Both ways are fine, use either. |
Both ways are fine, use either. |
||
| − | + | === Execute <code>install-lingoport-plugins.sh </code> === |
|
This way to setup involves downloading the <code>jenkins-cli.jar</code> file, setting some variables, and running the script. |
This way to setup involves downloading the <code>jenkins-cli.jar</code> file, setting some variables, and running the script. |
||
| − | + | ==== Download <code>jenkins-cli.jar</code> ==== |
|
| + | === Use the Jenkins interface === |
||
| + | If executing the script does not work for you, an alternative is to setup all the plugins via the Jenkins interface. |
||
The following Jenkins plugins are required. To see what plugins are installed, go to '''Jenkins -> Manage Jenkins -> Manage Plugins''' and select the '''Installed''' tab. |
The following Jenkins plugins are required. To see what plugins are installed, go to '''Jenkins -> Manage Jenkins -> Manage Plugins''' and select the '''Installed''' tab. |
||
Revision as of 22:23, 22 September 2015
Contents
Install Jenkins
Download Jenkins from jenkins-ci.org, install it, and run it. Must be version 1.609 or later. Otherwise, the location of the 'workspace' may vary, causing real problems! Jobs created by this version must have the workspace located under $JENKINS_HOME/jobs/$JOBNAME/workspace.
Set up Jenkins Plugins
You may setup the plugins used by LRM in two ways:
- Run the setup script using jenkins-cli.jar at the command line
- Install the plugins from the Jenkins interface
Both ways are fine, use either.
Execute install-lingoport-plugins.sh
This way to setup involves downloading the jenkins-cli.jar file, setting some variables, and running the script.
Download jenkins-cli.jar
Use the Jenkins interface
If executing the script does not work for you, an alternative is to setup all the plugins via the Jenkins interface.
The following Jenkins plugins are required. To see what plugins are installed, go to Jenkins -> Manage Jenkins -> Manage Plugins and select the Installed tab.
- Authorization Strategy Plugin (Or another authentication/authorization plugin)
Throttle
Go to Configure (Configure System) and under the Throttle Concurrent Builds, add a category (MAIN for instance) with 1 Maximum Total Concurrent Builds and 1 Maximum Concurrent Builds Per Node.
Every Jenkins job MUST have this throttle setup.
Note
A quick note for the relationship between the TOKEN necessary for the lingotekcall back and security:
1) The plugin is Build Authorization Token Root Plugin, https://wiki.jenkins-ci.org/display/JENKINS/Build+Token+Root+Plugin It must be installed. However, if no security is set, jobs cannot be triggered remotely using a TOKEN!!! So ...
2) Make sure security is set. The typical one is first set under Configure Global Security in Manage Jenkins for 'Matrix Security' and 'Using Jenkins Own Database'. Once this is set (as opposed to anonymous everything), one can then use the Build Authorization Token Root in the lingotekcall job: Set the Token to 'LINGOSQUARE'
