From 04226c16cc6e9c0084b72ca36ec6e5676b30a027 Mon Sep 17 00:00:00 2001 From: esdrasrenan Date: Tue, 16 Dec 2025 22:26:44 -0300 Subject: [PATCH] docs: adiciona troubleshooting para CI/CD Forgejo MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adiciona solucoes para problemas comuns: - Regeneracao de hooks quando workflows nao disparam - Correcao de erro de LevelDB lock - Reinicio do runner apos reinicio do Forgejo 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- docs/FORGEJO-CI-CD.md | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/docs/FORGEJO-CI-CD.md b/docs/FORGEJO-CI-CD.md index 8b9372f..fb1cc56 100644 --- a/docs/FORGEJO-CI-CD.md +++ b/docs/FORGEJO-CI-CD.md @@ -249,13 +249,33 @@ journalctl -u forgejo-runner --no-pager -n 50 # Verificar conectividade curl -s https://git.esdrasrenan.com.br/api/healthz + +# Se o runner mostrar erro "404 Not Found" apos reinicio do Forgejo: +systemctl restart forgejo-runner ``` -### Workflow nao dispara +### Workflow nao dispara apos push 1. Verificar se o arquivo esta em `.forgejo/workflows/` 2. Verificar se Actions esta habilitado no repositorio (Settings > Actions) 3. Verificar se o runner esta online (Settings > Actions > Runners) +4. **Regenerar hooks do repositorio:** + ```bash + docker exec -u 1000:1000 $(docker ps -q --filter "name=forgejo_forgejo") \ + /usr/local/bin/gitea admin regenerate hooks --config /data/gitea/conf/app.ini + ``` + +### Erro de LevelDB Lock (queue nao inicia) + +Se o Forgejo mostrar erro `unable to lock level db at /data/gitea/queues/common`: + +1. O stack.yml ja usa `FORGEJO__queue__TYPE=channel` para evitar esse problema +2. Se o erro persistir, limpe o diretorio de queues: + ```bash + docker exec $(docker ps -q --filter "name=forgejo_forgejo") \ + rm -rf /data/gitea/queues/* + docker service update --force forgejo_forgejo + ``` ### Erro de permissao no deploy