Todos los artículos

Getting Started

Qué es CICDoo Primeros pasos: el asistente de incorporación El Panel y el Mapa de Infraestructura

Concepts

Etapas de producción, staging y desarrollo Dominios, subdominios y SSL Versiones y ediciones de Odoo (Community vs Enterprise) Espacios de trabajo y colaboración en equipo

Servers

Añadir un servidor Dominios de servidor y DNS Usar un balanceador de carga Acciones de servidor: desplegar, registros y gráficos Deleting a server

Projects & Git

Crear un proyecto Conectar GitHub Project GitHub settings and webhook Conectar GitLab Ramas e instancias Etiquetar y filtrar proyectos Alta disponibilidad con nodos de aplicación Project environments, extensions and deletion

Instances & Console

Crear una instancia Reiniciar, detener y eliminar una instancia Fusionar ramas entre etapas Web IDE y acceso remoto SSH access to instances Explicación de los ajustes de la instancia Despliegues y la cola de trabajos

Agent Tasks

Qué son las tareas del agente Configurar las tareas del agente Ejecutar una tarea y revisar el resultado Tiempo de agente y recargas Agent insights and task filters

Monitoring & Backups

Monitorear tu instancia Copias de seguridad y restauración S3 storage, uploads and bulk backup actions Notificaciones de alerta (correo y SMS)

Workspaces & Permissions

Invitar a miembros del espacio de trabajo Permisos de los miembros y acceso a recursos Un miembro no puede ver o usar un recurso Audit log and server activity

Account & Security

Autenticación de dos factores (2FA) Ajustes de perfil e integraciones Contraseñas y recuperación de cuenta

Billing & Plans

Planes y precios Mejorar y gestionar tu suscripción Si una suscripción de proyecto queda sin pagar El programa de partners de canal Onboarding a client as a partner

Support & Tickets

Abrir un ticket de soporte Cómo obtener ayuda del equipo de CICDoo

Troubleshooting

Resolución de problemas: no se puede conectar un servidor Resolución de problemas: falló un despliegue Resolución de problemas: git push falla con 403 tras mover un repositorio Resolución de problemas: mi instancia está caída o lenta Resolución de problemas: problemas de dominio o SSL

Proyectos y Git

Project GitHub settings and webhook

How to use the GitHub tab of a project's settings to fix a missing push webhook, re-sync a moved repository, change the default branch and choose which GitHub credential the project uses.

Each project has its own GitHub settings, on the "GitHub" tab of the project settings. They control which repository and branch the project deploys, which GitHub credential it uses, and whether GitHub tells CICDoo about new pushes. The tab is meant for projects hosted on GitHub.

Opening the GitHub tab

You need permission to change the project's settings ("Project settings").

  1. On the Projects page, click "Settings" on the project's card. From the project console, you can also use the "Project Settings" link at the bottom of the sidebar.
  2. Click the "GitHub" tab.

At the top, the "GitHub Integration" card shows the repository, its description and a "View on GitHub" link.

Why the push webhook matters

When you push to a branch, or merge one branch into another, GitHub has to notify CICDoo so the matching instance is upgraded. That notification is the project's push webhook, created on your repository when the project is created. Without it, pushes and merges reach GitHub but your instances are never upgraded, and nothing looks wrong at first sight.

CICDoo checks every GitHub project once a day and tries to recreate a missing webhook. Creating it needs a GitHub account with admin access to the repository, so the daily retry can keep failing until you fix the access.

Fixing a missing push webhook

When the webhook is missing, the GitHub tab shows a "Push webhook missing" notice.

  1. Make sure the GitHub account connected to CICDoo has admin access to the repository. See Connecting GitHub.
  2. On the GitHub tab, click "Create webhook" in the "Push webhook missing" notice.
  3. Wait for "Webhook created successfully". The notice disappears.

If you see "Could not create the webhook. Check that GitHub is connected and has admin access to this repository.", ask a repository admin to connect their account or grant you admin access, then try again. After the webhook is in place, push again or restart the instance to deploy any commits that were missed. See Restarting, stopping and removing an instance.

Re-syncing a moved or renamed repository

The "Repository" field is read-only. If you transferred the repository to an organization or renamed it, pushes from your instances fail with a 403.

  1. On the GitHub tab, click "Re-sync from GitHub".
  2. Wait while CICDoo asks GitHub for the repository's current name. The page reloads with the new owner and name.
  3. Restart each instance of the project so it picks up the new address.

See Troubleshooting: git push fails with 403 after moving a repository.

Changing the default branch

The "Default Branch" is the branch used for the production instance.

  1. On the GitHub tab, change "Default Branch" to the branch name you want, for example main.
  2. Click "Save Changes" at the top right of the page.

The production instance switches to the new branch. Make sure the branch exists in the repository before saving.

Choosing how the project authenticates to GitHub

Under "Authentication", pick one:

  • "Standard": use your account's OAuth token, falling back to its classic token. This suits most projects.
  • "Classic token only": never use the OAuth token. Choose this when your organization does not allow granting access to OAuth apps.

To switch to a classic token:

  1. Select "Classic token only".
  2. Optionally paste a classic token into "Token for this project". Leave it empty to use your account's classic token. Use a project token when this repository lives in a different organization than your other projects.
  3. Click "Save Changes".
  4. Click "Re-sync from GitHub" to check that the selected credential can reach the repository.

If you choose "Classic token only" with no project token and no classic token on your account, saving is refused until you add one. A project token is stored on the platform and sent to your instance containers to clone the repository.

Note: Odoo Enterprise always needs a classic token, whatever you pick here. See Odoo versions and editions (Community vs Enterprise).

Related: Connecting GitHub, Merging branches between stages, Deployments and the job queue, Project environments, extensions and deletion.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Anterior Conectar GitHub Siguiente Conectar GitLab

¿Sigues atascado? Abre un ticket desde la app o habla con un ingeniero.