On 2020-07-13 07:08, Ryan Schmidt wrote:
On Jul 9, 2020, at 04:51, Roland van Laar wrote:
On 2020-07-09 03:51, Ryan Schmidt wrote:
Hi,
Is it possible to have a single buildmaster in which some workers are public
(their build logs can be seen by anybody) while other workers are private
(their logs can only be seen by specific logged in users)?
Do you mean workers, or specific builders?
A Worker is a vm/machine on which the builders run.
A builder is a buildfactory, which contains the executable steps of a build.
What is the data you want to protect from publicity?
I want to set up three builders on a new worker. All of the builders on that
worker should be protected. I want to be able to see the logs of those build
myself when I log in to the buildmaster web interface, and I want to be able to
grant specific other users access to do that, but the general public accessing
the buildmaster and any other logged in user should not be able to see those
logs. There are also other workers that have instances of those builders; they
are and should remain public.
My assumption is that this is not possible and that I should set up a second
private buildmaster.
There's not a configuration flag that can be used.
It is possible to write the necessary code for it.
Do you mean adding code to my configuration or modifying the buildbot code? Any
other pointers you can offer?
I would read the documentation about the authorization:
https://docs.buildbot.net/2.8.2/manual/configuration/www.html#authorization-rules
It's my understanding that only endpoints and roles can be matched, e.g.
read permission to see builds.
Not to differentiate between builds.
If it's not going to be very straightforward I'll probably go with my separate
private buildmaster plan, since my familiarity with buildbot source code and
python in general is fairly low.
In that case, it's easier to set up a second buildbot.
_______________________________________________
users mailing list
users@buildbot.net
https://lists.buildbot.net/mailman/listinfo/users
