07:50 <Guest34> hi how can i add javascript and/or css to the existing buildbot webpages .. and trigger step -run give the option to show None/Problems/All - it shows "hidden" steps as problems can i not show the hidden steps under "Problems" ?

19:46 <antranigv> Hey all. How can I make sure that only one build will run at a time? or maybe how can I make two build exclusive and wait? basically, I have two builds and I want them to run in order

19:55 <glogan> antranigv: worker or master lock to build exclusively. Doesn't guarantee order.

19:55 <glogan> use a dependent scheduler to link them in order

19:55 <glogan> which, now that I think about it, would also mean you could skip the locks

19:55 <antranigv> how about no order, as long as they don't run at the same time

19:55 <antranigv> the problem is

19:55 <antranigv> I have a single source (git repo) which should build two elixir applications

19:56 <antranigv> When they run the steps at the same time, Hex (the package manager) crashes

19:57 <antranigv> I can either use nextBuild

19:57 <antranigv> or maybe a trigger sched

19:57 <antranigv> glogan any thoughts?

19:58 <glogan> if you don't care about order, a masterlock is probably easiest

19:58 <glogan> especially if you have it working aside from the crashes

19:58 <glogan> if you've got more than one worker and are fine with building all the things except that only one build can run on a worker at a time, then you want a workerlock

20:24 <antranigv> One worker, builds one-by-one. Okay, this good! thanks a lot glogan

20:24 <antranigv> TIL about Manhole

20:25 <antranigv> One day, when our company becomes famous, I'll add us to the "who uses buildbot" list

20:25 <glogan> is there a list?

20:29 <antranigv> Yes, glogan https://github.com/buildbot/buildbot/wiki/SuccessStories

20:29 <antranigv> glogan where can I read about masterlock?

20:30 <glogan> https://docs.buildbot.net/latest/manual/configuration/interlocks.html

20:30 <glogan> under examples

20:30 <antranigv> glogan thanks. I still don't get it, I'll try to read the code

20:31 <antranigv> oh I can use the locks in steps

20:31 <antranigv> which is what I need, for things like `pkg` and pip and Hex

20:34 <glogan> yep

20:34 <glogan> can also use them on builders/schedulers

20:35 <antranigv> I wonder if there's a way to say "just do one build at a time"

20:35 <antranigv> there was like max_count I think

20:35 <glogan> https://github.com/opencast/opencast-project-infrastructure/blob/6d13b3a8be61fa380dc5a47f7025bf91048e696b/ansible-buildbot-cluster/roles/buildbot-config/templates/master.cfg#L93

20:35 <glogan> one job at a time, on a per-worker basis

20:36 <glogan> https://github.com/opencast/opencast-project-infrastructure/blob/master/ansible-buildbot-cluster/roles/buildbot-config/templates/builders.py#L55

20:36 <glogan> one job at a time, on a per-builder basis

20:37 <glogan> I needed to be able to track three branches, and be able to build them all independently. But only one build at a time, on a per-branch basis. And only one build per node since our workers don't have the memory do to more.

20:37 <antranigv> glogan how can I buy you coffee?

20:37 <glogan> :)

20:37 <antranigv> or tea, if you prefer

20:48 <antranigv> glogan it worked! thank you! <3

20:49 <glogan> +1

23:29 <antranigv> oh god I can't believe there's no proper buildbot slack reporter