security

Security in Jenkins

Session Type: 
Standard [35 minutes]
Speakers

Anyone setting up continuous integration using the popular Jenkins (or Hudson) server for more than a handful of people will soon need to consider security. How can you be identified to the server? How do your SCM commits get associated with that identity? Who should be allowed to do what? And how can Jenkins identify itself to other services, like GitHub or Maven repositories, when it needs to publish results?

Schedule info

Status: 
Declined

Audience

Track: 
ALM Connect
Experience level: 
Intermediate

Copyright © 2013 The Eclipse Foundation. All Rights Reserved.