Can I configure Hudson to prevent certain users from accessing certain users?

Question

I have different projects that are periodically created and tested on the Hudson server, but I do not want every company employee to see published artifacts for each project.

Initially, the project-based security key seemed first, but after many tests, I found that granting general read permissions is mandatory if you want users to be able to read anything on the hudson server.

So, at the end of the read permission is binary: either you grant global read permission or block everything, is it correct?

Answer 1

Has it been tested with the latest version, but I am using the matrix setting. I gave Anonymous total number of reads. Thus, they can see the login screen when they type {{ http: // servername: port / }}, but do not give them access to the tasks. In the works themselves, I set up users who should really see the work. It works like a charm.

UPDATE: In the meantime, I found out that you can use authenticated instead of Anonymous . This allowed access to Hudson / Jenkins via links in messages with a build error. Now everyone receives a login dialog box and after logging in they are immediately on the task of interest.

Answer 2

After trying to do something similar to you with the Hudson authorization settings, I came to the same conclusion as you.