Figure 7.20. Configuring project-based security
The way this works is easiest to understand with a few practical examples. In Figure 7.19, “Project-based
security”, for instance, no permissions have been granted to the anonymous user, so by default all build
jobs will remain invisible until a user signs on. However, we are using project-based security, so we
can override this on a project-by-project basis. In Figure 7.20, “Configuring project-based security”, for
example, we have set up the game-of-life project to have read-only access for the special “anonymous”
user.
When you save this configuration, unauthenticated users will be able to see the game-of-life project
in read-only mode (see Figure 7.21, “Viewing a project”). This same principle applies with all of the
project-specific permissions.
Figure 7.21. Viewing a project
Note that Jenkins permissions are cumulative—at the time of writing, there is no way to revoke a system-
wide permission for a particular project. For example, if the anonymous user has read-access to build
jobs at the system level, you can’t revoke read-only access for an individual project. So when using