Sometimes, specially if you have multiple components, the builds can be more than the allow limit of parallel builds, this task is to allow queuing the builds to a higher limit to be able to cope with the sudden build burst.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | LucasWerkmeister | T320140 Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes | |||
| Resolved | matmarex | T319707 Migrate dtcheck from Toolforge GridEngine to Toolforge Kubernetes | |||
| Resolved | Legoktm | T320062 Migrate steve-adder from Toolforge GridEngine to Toolforge Kubernetes | |||
| Resolved | Legoktm | T320011 Migrate rfa-voting-history from Toolforge GridEngine to Toolforge Kubernetes | |||
| In Progress | dcaro | T194332 [builds-api,components-api,webservice,jobs-api] Make Toolforge a proper platform as a service with push-to-deploy and build packs | |||
| Resolved | dcaro | T393564 [Hypothesis] WE6.3.10 start a beta for the push-to-deploy features | |||
| Resolved | DamianZaremba | T401851 [components-api,beta] Image should only be build once when re-used in components | |||
| Open | None | T401894 [builds-api] Allow queuing builds |
Event Timeline
Comment Actions
This is not critical now that components-api will be the one waiting for the builds to finish T402568: [components-api] Queue builds when the build queue is full