Codeberg/Community
54
325
Fork
You've already forked Community
12

Woodpecker can't pull my Pages branch in a submodule #2214

Open
opened 2025年11月17日 07:06:43 +01:00 by clayote · 3 comments

Comment

I'm hosting the documentation for Lisien in the pages branch of that repository, which is also registered as the docs submodule, so that sphinx has somewhere to output to.

I'm setting up my very first Woodpecker pipeline for Lisien. It seems to clone the repository correctly, at first. Then it tries to update the submodules, but it can't update docs because it lacks... exactly the same host key that the main branch has, I'd think? It'd be weird for one repository to have two host keys, right?

+ git init --object-format sha1 -b main
Initialized empty Git repository in /woodpecker/src/codeberg.org/clayote/Lisien/.git/
+ git config --global --replace-all safe.directory /woodpecker/src/codeberg.org/clayote/Lisien
+ git remote add origin https://codeberg.org/clayote/Lisien.git
+ git fetch --no-tags --depth=1 --filter=tree:0 origin +583046b0e77fdbe48b3273cce4cda87d6c8f24bf:
From https://codeberg.org/clayote/Lisien
 * branch 583046b0e77fdbe48b3273cce4cda87d6c8f24bf -> FETCH_HEAD
+ git reset --hard -q 583046b0e77fdbe48b3273cce4cda87d6c8f24bf
+ git submodule update --init --recursive --depth=1 --recommend-shallow
Submodule 'docs' (git@codeberg.org:clayote/Lisien.git) registered for path 'docs'
Cloning into '/woodpecker/src/codeberg.org/clayote/Lisien/docs'...
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@codeberg.org:clayote/Lisien.git' into submodule path '/woodpecker/src/codeberg.org/clayote/Lisien/docs' failed
Failed to clone 'docs'. Retry scheduled
Cloning into '/woodpecker/src/codeberg.org/clayote/Lisien/docs'...
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@codeberg.org:clayote/Lisien.git' into submodule path '/woodpecker/src/codeberg.org/clayote/Lisien/docs' failed
Failed to clone 'docs' a second time, aborting
exit status 1
### Comment I'm hosting the documentation for [Lisien](https://codeberg.org/clayote/Lisien) in the `pages` branch of that repository, which is also registered as the `docs` submodule, so that `sphinx` has somewhere to output to. I'm setting up my very first Woodpecker pipeline for Lisien. It seems to clone the repository correctly, at first. Then it tries to update the submodules, but it can't update `docs` because it lacks... exactly the same host key that the main branch has, I'd think? It'd be weird for one repository to have two host keys, right? ``` + git init --object-format sha1 -b main Initialized empty Git repository in /woodpecker/src/codeberg.org/clayote/Lisien/.git/ + git config --global --replace-all safe.directory /woodpecker/src/codeberg.org/clayote/Lisien + git remote add origin https://codeberg.org/clayote/Lisien.git + git fetch --no-tags --depth=1 --filter=tree:0 origin +583046b0e77fdbe48b3273cce4cda87d6c8f24bf: From https://codeberg.org/clayote/Lisien * branch 583046b0e77fdbe48b3273cce4cda87d6c8f24bf -> FETCH_HEAD + git reset --hard -q 583046b0e77fdbe48b3273cce4cda87d6c8f24bf + git submodule update --init --recursive --depth=1 --recommend-shallow Submodule 'docs' (git@codeberg.org:clayote/Lisien.git) registered for path 'docs' Cloning into '/woodpecker/src/codeberg.org/clayote/Lisien/docs'... Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. fatal: clone of 'git@codeberg.org:clayote/Lisien.git' into submodule path '/woodpecker/src/codeberg.org/clayote/Lisien/docs' failed Failed to clone 'docs'. Retry scheduled Cloning into '/woodpecker/src/codeberg.org/clayote/Lisien/docs'... Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. fatal: clone of 'git@codeberg.org:clayote/Lisien.git' into submodule path '/woodpecker/src/codeberg.org/clayote/Lisien/docs' failed Failed to clone 'docs' a second time, aborting exit status 1 ```

@clayote wrote in #2214 (comment):

I'm setting up my very first Woodpecker pipeline for Lisien. It seems to clone the repository correctly, at first. Then it tries to update the submodules, but it can't update docs because it lacks... exactly the same host key that the main branch has, I'd think? It'd be weird for one repository to have two host keys, right?

The error from git is misleading, it's trying to do SSH but I don't think any SSH key is configured. I would suggest that https://codeberg.org/clayote/Lisien/src/branch/main/.gitmodules#L3 uses a HTTPS link instead.

@clayote wrote in https://codeberg.org/Codeberg/Community/issues/2214#issue-2677226: > I'm setting up my very first Woodpecker pipeline for Lisien. It seems to clone the repository correctly, at first. Then it tries to update the submodules, but it can't update `docs` because it lacks... exactly the same host key that the main branch has, I'd think? It'd be weird for one repository to have two host keys, right? The error from git is misleading, it's trying to do SSH but I don't think any SSH key is configured. I would suggest that https://codeberg.org/clayote/Lisien/src/branch/main/.gitmodules#L3 uses a HTTPS link instead.
Author
Copy link

Thanks, that worked.

Is this documented anywhere in Codeberg's help files? I'm not sure where it should go...

Thanks, that worked. Is this documented anywhere in Codeberg's help files? I'm not sure where it should go...

I'm not sure if this is a Codeberg problem or a Woodpecker limitation, but in general having SSH URLs for submodules is quite uncommon.

I'm not sure if this is a Codeberg problem or a Woodpecker limitation, but in general having SSH URLs for submodules is quite uncommon.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2214
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?