Difference between revisions of "Localyzer Jenkins Plugins"
(→Jenkins) |
|||
| Line 3: | Line 3: | ||
Download Jenkins from [https://jenkins-ci.org/ jenkins-ci.org], install it, and run it. |
Download Jenkins from [https://jenkins-ci.org/ jenkins-ci.org], install it, and run it. |
||
| + | The following Jenkins plugins are required. |
||
| − | Make sure to install the following Jenkins plugins: |
||
* [https://wiki.jenkins-ci.org/display/JENKINS/Build+Token+Root+Plugin Build Token Root Plugin] |
* [https://wiki.jenkins-ci.org/display/JENKINS/Build+Token+Root+Plugin Build Token Root Plugin] |
||
Revision as of 15:02, 14 April 2015
Jenkins
Download Jenkins from jenkins-ci.org, install it, and run it.
The following Jenkins plugins are required.
- Authorization Strategy Plugin (Or another authentication/authorization plugin)
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 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 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'
