Open waja opened 8 months ago
Running the CI pipeline on a forgejo runner fails actually with:
::group::Install build dependencies
[command]/usr/bin/docker exec dropbear bash -c apt-get build-dep -yq -t 'bullseye-backports' '/workspace/waja/action-debian-package/dropbear' || apt-get build-dep -yq '/workspace/waja/action-debian-package/dropbear'
E: Unsupported file /workspace/waja/action-debian-package/dropbear given on commandline
E: Must specify at least one package to check builddeps for
E: Unsupported file /workspace/waja/action-debian-package/dropbear given on commandline
E: Must specify at least one package to check builddeps for
::error::The process '/usr/bin/docker' failed with exit code 100
You can take a look into it at https://git.uncompleted.org/waja/action-debian-package/actions/runs/4#jobstep-4-4404. I haven't found the issue behind this, cause /workspace/waja/action-debian-package/dropbear
exists and has the dropbear files into it.
hmmm ... seems like the directory is empty in the container:
::group::Check sourceDirectory
[command]/usr/bin/docker exec dropbear ls -la /workspace/waja/action-debian-package/dropbear
total 8
drwxr-xr-x 2 root root 4096 Jan 4 18:36 .
drwxr-xr-x 9 root root 4096 Jan 4 18:43 ..
::endgroup::
Hmm, some problem with git repo checkout? Is this directory empty also on the runner?
Actually, I suspect valid_volumes
from runners config. I'm looking into it.
Github Actions can be used outside the Github infrastructure, for example Forgejo can use Actions (see https://forgejo.org/docs/v1.21/user/actions/).
The action seems not support to be used outside the Github infrastructure (yet).