diff --git a/backend/configs/gitea.py b/backend/configs/gitea.py index d506b68..c9406ee 100644 --- a/backend/configs/gitea.py +++ b/backend/configs/gitea.py @@ -4,7 +4,28 @@ from steps.docker import DockerSwarmCheck, DockerSwarmDeploy from steps.git import GitClone, CheckoutMerged, GitUnmerge from steps.shared_state import SharedStateHolderInMemory -clone = GitClone(url="https://github.com/rudolf1/uber_backup.git", branchNamePrefix="ansible") +# Dual-remote clone for the ansible mirror (the deploy target, not brencher itself). +# - gitea_hermes is where the feature branch lives (hermes/ansible:*) +# - gitea_admin is the live-deploy source (where brencher-bot reads compose files from) +# +# Why not github? github.com is unreachable from the brencher container -- the +# proxy returns HTTP 403 on CONNECT tunnel, so the URL would always fail to +# fetch. See backend/configs/docker_socket_proxy.py for the same migration. +# +# Why drop branchNamePrefix? GitClone only applies its prefix refspec to a +# remote named "origin" (backend/steps/git.py ~L104); neither remote here is +# named "origin", so the prefix would be a silent no-op. Both remotes fetch +# their full refset instead. +# +# Why two remotes? The deploy step (DockerSwarmDeploy) checks out a specific +# branch and uses the resulting checkout as wd for the compose path. With +# gitea_hermes as primary, feature branches opened in the fork are picked up; +# gitea_admin provides the live-deploy source as a fallback / for cross-fork +# PRs. This matches the form in backend/configs/brencher.py after PR #3. +clone = GitClone(remotes=[ + {"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/ansible"}, + {"name": "gitea_admin", "url": "https://gitea.rudolf.keenetic.link/admin/ansible"}, +]) dockerSwarmCheck = DockerSwarmCheck( stack_name="gitea",