`woodpecker exec .woodpecker/ubuntu.yml` has no repo available

[wez]

Component

cli

Describe the bug

Running a pipeline directly like this:

$ woodpecker exec .woodpecker/ubuntu.yml
...
[build:L188:17s] + ./get-deps.sh
[build:L189:17s] /bin/sh: 30: ./get-deps.sh: not found

fails to mount the repo, so fails to run the get-deps.sh script that is present in the repo.

However, running it like this:

$ woodpecker exec .
# ci.yml

# ci.yml

# rust.yml

# ci.yml

# ci.yml

# ci.yml

# ci.yml

# ci.yml

# codecov.yml

# audit.yaml

# benchmarks.yaml

# coverage.yaml

# test.yaml

# ci.yml

# FUNDING.yml
...

worryingly enumerates all the various yaml files in my working copy (those shown are from misc .cache and .github directories) as shown above, as if it were trying to run those, but does mount the repo and is able to run the script from inside it.

My expectation is that I can specify the pipeline I want to run based on the --help output:

$ woodpecker exec --help
...
USAGE:
   woodpecker-cli exec [command options] [path/to/.woodpecker.yaml]

and have the repo mounted in the pipeline at the same time.

System Info

$ woodpecker --version
woodpecker-cli version 1.0.2

Additional context

No response

Validations

• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
• [X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

[wez]

If I can be frank, the docs for the CLI are particularly light on meaningful detail. While they appear to have a list of all of the possible options but there is no explanation for anything. I only found the exec . thing by reading through the issues on github. It would be great to have a getting started section that shows how best to use exec!

My goal in this situation is to build up my pipelines without making dozens of pushes to dial things in.

[qwerty287]

What do you would like to change? Would just more documentation be enough?

[wez]

my perception is that this command doesn't work as advertised by its help; the repo needs to be mounted in the first case.

In the second case, I would like some other way to scope the workflow that is being run, and not have woodpecker look through random directories