Make local backend work with cli exec

[6543]

Currently if you try to exec a pipeline via the cli tool and use the local backend, all files are missing.
This will detect this specific case and use the new added option in the local backend to specify a execution directory upfront.

---

Sponsored by Kithara Software GmbH

[woodpecker-bot]

Deploying preview to https://woodpecker-ci-woodpecker-pr-4102.surge.sh

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 26 lines in your changes missing coverage. Please review.

Project coverage is 26.94%. Comparing base (b1cf44a) to head (06e5a2a).

Files with missing lines	Patch %	Lines
pipeline/backend/local/local.go	0.00%	22 Missing ⚠️
cli/exec/exec.go	0.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4102      +/-   ##
==========================================
- Coverage   26.98%   26.94%   -0.04%     
==========================================
  Files         394      394              
  Lines       27395    27414      +19     
==========================================
- Hits         7393     7388       -5     
- Misses      19302    19326      +24     
  Partials      700      700              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[6543]

@anbraten if you know an better way to do:

woodpecker-cli.exe exec --backend-engine local --pipeline-event push --commit-branch main

to test local backend via cli in windows / linux please tell :)

[anbraten]

Will do some testing. Fyi #3967 might be quite interesting for you.

[6543]

Yes thus might allow more :)

Should i hide the flag and undocument it so we have it working now and can improve it later?

[anbraten]

The usage of the local property was somehow not compatible with the local backend. This fixes it for me so I was able to run:

go run ../cmd/cli/ exec --pipeline-event push --commit-branch main --backend-engine local --local

https://github.com/woodpecker-ci/woodpecker/compare/main...anbraten:local-path?expand=1

[6543]

I looked at your solution, this has 2 problems:

1. the 'repo-path' is now (miss-)used at the local backend even if it never was registered there (the lib we have do handle that but its outside of our convention)
2. artifacts that should not be there like temporary exec files are now stored inside the current repo, witch differs completly on how the backend is executed with server&agent combi
3. the bug mentioned in 2. affects docker backend if exec via cli now too (because of the removed volume)

the only thing i could addopt in my patch from your suggestion would be 1. witch breaks the convention ...
... not sure if this makes maintaining this harder...

[6543]

what i could do and did, is to hide that option from the user: 7101cdb