woodpecker/pipeline/backend
Alexander Matyushentsev ee969979c6
fix: backend auto-detection should be consistent (#1618)
Closes https://github.com/woodpecker-ci/woodpecker/issues/1617

The `woodpecker exec` auto-detects the backend by iterating over a map
of backends. However, since Go 1 the runtime randomizes map iteration
order, so a random backend might be chosen during each execution.

PR changes to auto-detection to iterate over the backends list with
predefined priority: `docker`, `local`, `ssh`, `kubernetes`.

---------

Signed-off-by: Alexander Matyushentsev <AMatyushentsev@gmail.com>
2023-03-13 09:07:41 +02:00
..
common GenerateScript should not return encoded script (#1397) 2022-11-06 13:36:34 +01:00
docker fix: docker backend should not close 'engine.Tail' result (#1616) 2023-03-12 16:01:09 +01:00
kubernetes Ensure the SharedInformerFactory closes eventually (#1585) 2023-02-16 00:54:33 +01:00
local Use modern error handling and enforce it via lint (#1327) 2023-02-02 00:08:02 +01:00
ssh GenerateScript should not return encoded script (#1397) 2022-11-06 13:36:34 +01:00
types Add option to ignore failures on steps (#1219) 2022-11-15 19:47:27 +01:00
backend.go fix: backend auto-detection should be consistent (#1618) 2023-03-13 09:07:41 +02:00