woodpecker/pipeline/backend
Ben Cordero 3158980d3e
Get workflow id from clone steps (#1839)
When in local mode, `getWorkflowIDFromStep` can handle normal steps with
a name like `wp_01h2a6qggwz68zekrkbwqq9rny_0_step_0`.

However, it will fail on clone (unless `skip_clone: true`) with an
`invalid step name` error.

```
invalid step name wp_01h2a2ebppp43bwjdfdsyj1m6m_0_clone
```

This patch handles either `_stage_` or `_clone` as the separator that
the local backend can use to extract the workflowID.
2023-06-08 03:33:23 +02:00
..
common GenerateScript should not return encoded script (#1397) 2022-11-06 13:36:34 +01:00
docker Rework log streaming and related functions (#1802) 2023-06-06 09:52:08 +02:00
kubernetes Allow setting resources for kubernetes on a per-step basis (#1767) 2023-06-04 00:50:08 +02:00
local Get workflow id from clone steps (#1839) 2023-06-08 03:33:23 +02:00
ssh Various enhancements in configuration (#1645) 2023-03-19 20:24:43 +01:00
types Rework log streaming and related functions (#1802) 2023-06-06 09:52:08 +02:00
backend.go Various enhancements in configuration (#1645) 2023-03-19 20:24:43 +01:00