Difference between revisions of "Localyzer Jenkins Plugins"
m |
|||
| Line 2: | Line 2: | ||
* Build Token Root Plugin[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] |
||
| − | * |
+ | * [https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin Credential Plugin] |
| − | * |
+ | * [https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin Git Client Plugin] |
| − | * |
+ | * [https://wiki.jenkins-ci.org/display/JENKINS/GitHub+API+Plugin GitHub API Plugin] |
| − | * |
+ | * [https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin GitHub Plugin] |
*Matrix Authorization Strategy Plugin (Or another authentication/authorization plugin)[https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Authorization+Strategy+Plugin] |
*Matrix Authorization Strategy Plugin (Or another authentication/authorization plugin)[https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Authorization+Strategy+Plugin] |
||
Revision as of 19:52, 30 March 2015
The following Jenkins plugins must be installed:
- Build Token Root Plugin[1]
- Matrix Authorization Strategy Plugin (Or another authentication/authorization plugin)[2]
- Throttle Concurrent Builds Plugin[3]
- 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'
