Changes to approval

We’ve recently introduced a change to how Wait for approval behaves in sequential pipelines in Buddy.

What changed?

From now on, runs that reach a Wait for approval action will block the execution queue. This means that if a pipeline run is waiting for approval, the next runs in the queue will not start until that approval step is resolved.

Why we made this change?

Previously, approval steps did not block the queue. Thiss allowed for multiple runs to pile up, it also created a misleading situation where you could have multiple executions waiting for approval, while in practice only the latest run was relevant.

Image loading...

Older runs would sit idle despite no longer being relevant, cluttering pipelines and making it unclear which run should be approved. On top of that, stale runs often couldn’t be approved because newer executions had already modified the cache.

Image loading...

Restoring previous behavior

If you prefer not to block the queue, you can achieve this by enabling a "New run terminates runs in progress for the same git ref" flag in the pipeline settings.

Image loading...

With this flag enabled, new executions will automatically cancel the older ones and only the most revent run will continue. This flag is disabled by default.