Add setting for concurrent builds #110

New Issue

Jef Roosens · 2022-02-27T08:22:18Z

Jef Roosens commented

2022-02-27 08:22:18 +00:00

I suggest an env var, VIETER_MAX_CONCURRENT_BUILDS, which sets how many builds can be running at once. Implementation should be fairly simple:

we currently already have a for loop that checks every 5s whether the build container has finished. This could be expanded to make it check for multiple containers, and at the start of each iteration, we check whether there's a new spot free. Because the check itself is synchronous, no issues should arise from changing the same variable concurrently.

I suggest an env var, `VIETER_MAX_CONCURRENT_BUILDS`, which sets how many builds can be running at once. Implementation should be fairly simple: we currently already have a for loop that checks every 5s whether the build container has finished. This could be expanded to make it check for multiple containers, and at the start of each iteration, we check whether there's a new spot free. Because the check itself is synchronous, no issues should arise from changing the same variable concurrently.

Jef Roosens added this to the 0.2.0 milestone 2022-02-27 08:22:18 +00:00

Jef Roosens added the

enhancement

label 2022-02-27 08:22:18 +00:00

Jef Roosens referenced this issue

2022-02-27 08:22:32 +00:00

Build system roadmap #106

Jef Roosens modified the milestone from 0.2.0 to 0.3.0

2022-03-29 11:48:50 +00:00

Jef Roosens modified the milestone from 0.3.0 to 0.4.0

2022-04-20 07:53:22 +00:00

Jef Roosens modified the milestone from 0.4.0 to 0.3.0