6543

I think the run_id is not within the docker backend ...

we need some server that do collect it & verify it's a legit request ... by do a callback and see if site exist?

> Sounds nice. My idea for the docker backend was to run each command step with `docker exec` instead of using the script and executing it via `docker run` once....

the core team has other prios ... but if somebody like to pick this issue up ... he just have to look into https://github.com/woodpecker-ci/woodpecker/tree/master/server/remote if he can can cover the...

I did revert https://github.com/woodpecker-ci/woodpecker/pull/877 via https://github.com/woodpecker-ci/woodpecker/commit/e2e094cfda87becedf7a37d6077fabea2c97ebb5 you can add it back in this pull - it need just more work ... PS: this patch do not solve the underlaying issue

@qwerty287 #949 should make the whole pipeline functions way more readable :)

please resolve merge conflict

to reproduce: 1. clone this repo into your local test env 2. enable ci for it 3. change a line in Makefile expect: - multible piplenes still run like "docker"...

at some point I'll also have a look at this ... as I dislike how global pipeline filter do (internaly) work atm

look's like a podman issue witch can not create networks :thinking: