00:45
kkleine has quit [Ping timeout: 264 seconds]
09:10
zware has quit [Ping timeout: 260 seconds]
09:10
zware has joined #buildbot
09:12
kraiskil has joined #buildbot
09:26
kraiskil has quit [Ping timeout: 265 seconds]
09:39
kraiskil has joined #buildbot
10:00
kraiskil has quit [Ping timeout: 264 seconds]
10:13
kraiskil has joined #buildbot
10:33
Rh0nda is now known as Rhonda
10:41
kraiskil has quit [Ping timeout: 256 seconds]
11:45
kraiskil has joined #buildbot
14:37
kraiskil has quit [Ping timeout: 240 seconds]
15:40
kraiskil has joined #buildbot
20:22
medfly has joined #buildbot
20:23
<
medfly >
I wonder if anyone else shares my reluctance to have results visible directly from the master, or I need to DIY a way to do this
20:24
<
medfly >
just a little paranoid since the thing I'm replacing is also used to do release builds
21:24
kraiskil has quit [Ping timeout: 240 seconds]
21:37
kraiskil has joined #buildbot
21:43
medfly has quit [Ping timeout: 240 seconds]
21:54
kraiskil has quit [Ping timeout: 240 seconds]
22:09
kraiskil has joined #buildbot
22:15
kraiskil has quit [Ping timeout: 246 seconds]
22:29
kkleine has joined #buildbot
23:45
p12tic has joined #buildbot
23:47
kkleine has quit [Ping timeout: 260 seconds]
23:52
<
p12tic >
medfly: What kind of results? Build logs and so on? Currently there is no proper boundary to hide the build results depending on who views them.
23:54
<
p12tic >
But you can easily limit who can start builds. There are few other ways to affect Buildbot if we're not talking about DoSing the instance