could not load config from forge: %!w() #248

gustavblass commented 2025年05月18日 18:26:35 +02:00

For my repo commons-email I set up

• .woodpecker/tests.yaml to conduct tests whenever any branch is pushed to and
• .woodpecker/javadocs.yaml to deploy the Javadocs to Codeberg Pages whenever a tag is pushed to master.

While the CI tests work fine, the Javadocs deployment fails with the message could not load config from forge: %!w(), before the pipeline even starts.

What did I do wrong?

For my repo [`commons-email`](https://codeberg.org/GustavVirtualMachine/commons-email) I set up - [`.woodpecker/tests.yaml`](https://codeberg.org/GustavVirtualMachine/commons-email/src/branch/master/.woodpecker/tests.yaml) to conduct tests whenever any branch is pushed to and - [`.woodpecker/javadocs.yaml`](https://codeberg.org/GustavVirtualMachine/commons-email/src/branch/master/.woodpecker/javadocs.yaml) to deploy the Javadocs to Codeberg Pages whenever a tag is pushed to master. While the CI tests work fine, the Javadocs deployment [fails](https://ci.codeberg.org/repos/14712/pipeline/4/errors) with the message `could not load config from forge: %!w()`, before the pipeline even starts. What did I do wrong?

martins-avots commented 2025年05月19日 10:12:53 +02:00

Hi,

could not load config from forge: %!w() seems to indicate, that something is missing regarding the container: https://github.com/woodpecker-ci/woodpecker/issues/4850
It seems to me, that the image codeberg.org/gustavvirtualmachine/ubuntu-gvm does not exist,
whereas the tests workflow contains an existing image URL.

Hi, `could not load config from forge: %!w()` seems to indicate, that something is missing regarding the container: https://github.com/woodpecker-ci/woodpecker/issues/4850 It seems to me, that the image `codeberg.org/gustavvirtualmachine/ubuntu-gvm` does not exist, whereas the tests workflow contains an existing image URL.

gustavblass commented 2025年05月19日 13:31:41 +02:00

The image does exist: https://codeberg.org/GustavVirtualMachine/-/packages/container/ubuntu-gvm/noble1

That page even suggests to use the following Docker command (with the same image name): docker pull codeberg.org/gustavvirtualmachine/ubuntu-gvm:noble1 🤷

The image does exist: https://codeberg.org/GustavVirtualMachine/-/packages/container/ubuntu-gvm/noble1 That page even suggests to use the following Docker command (with the same image name): `docker pull codeberg.org/gustavvirtualmachine/ubuntu-gvm:noble1` 🤷

martins-avots commented 2025年05月19日 14:11:28 +02:00

You're right.
I just did not find the git repo.
I even verified the presence now with a local docker pull.

Following might be a solution:
delete everything in the javadocs workflow until line 19 and see if the workflow works.
If not delete the last line, until the workflow works.
If the workflow works, you know, that the deleted steps are the problem.

Continue, until the problem is solved?

You're right. I just did not find the git repo. I even verified the presence now with a local docker pull. Following might be a solution: delete everything in the javadocs workflow until line 19 and see if the workflow works. If not delete the last line, until the workflow works. If the workflow works, you know, that the deleted steps are the problem. Continue, until the problem is solved?

gustavblass commented 2025年05月20日 22:11:09 +02:00

Now, the pipeline is started without the error occurring, although I didn't change anything. I assume it could be related to the recent hardware failure 🤔

Now, the pipeline is started without the error occurring, although I didn't change anything. I assume it could be related to the recent hardware failure 🤔