This chapter will introduce the various security options available to Jenkins administrators and users, explaining the protections offered, and trade-offs to ...
Missing: /url | Show results with:/url
This setting is controlled mainly by two axes: Security Realm, which determines users and their passwords, as well as what groups the users belong to.
Missing: /url | Show results with:/url
The permission Agent/Build requires access control for builds to be set up, as the build's authentication is checked, and not the user starting the build. In a ...
Missing: /url | Show results with:/url
Access Control is the primary mechanism for securing a Jenkins environment against unauthorized usage. Two facets of configuration are necessary for configuring ...
User Handbook · User Handbook Overview · Installing Jenkins · Platform Information · Using Jenkins · Pipeline · Blue Ocean · Managing Jenkins · Securing Jenkins ...
Missing: /url | Show results with:/url
Jenkins is a self-contained, open source automation server which can be used to automate all sorts of tasks related to building, testing, and delivering or ...
Missing: book/ | Show results with:book/
Jenkins builds pull requests sent by untrusted users, or employ a security model that limits trust in users allowed to configure one or more jobs, this also ...
Administrators may accidentally set up a security realm or authorization strategy in such a way that they are no longer able to administer or even access ...
The Jenkins project takes security seriously. We make every possible effort to ensure users can adequately secure their automation infrastructure.
Documentation. User Guide - Installing Jenkins - Jenkins Pipeline - Managing Jenkins - Securing Jenkins - System Administration - Troubleshooting Jenkins - ...