Alle Artikel

Getting Started

Was ist CICDoo Erste Schritte: der Onboarding-Assistent Das Dashboard und die Infrastrukturkarte

Concepts

Produktions-, Staging- und Development-Stages Domains, Subdomains und SSL Odoo-Versionen und -Editionen (Community vs. Enterprise) Workspaces und Teamzusammenarbeit

Servers

Einen Server hinzufügen Server-Domains und DNS Einen Load Balancer verwenden Server-Aktionen: Deploy, Logs und Diagramme Deleting a server

Projects & Git

Ein Projekt erstellen GitHub verbinden Project GitHub settings and webhook GitLab verbinden Branches und Instanzen Projekte mit Tags versehen und filtern Hochverfügbarkeit mit App-Knoten Project environments, extensions and deletion

Instances & Console

Eine Instanz erstellen Eine Instanz neu starten, stoppen und entfernen Branches zwischen Stages mergen Web-IDE und Fernzugriff SSH access to instances Instanzeinstellungen erklärt Deployments und die Job-Warteschlange

Agent Tasks

Was Agent-Aufgaben sind Agent-Aufgaben einrichten Eine Aufgabe ausführen und das Ergebnis prüfen Agent-Zeit und Aufstockungen Agent insights and task filters

Monitoring & Backups

Deine Instanz überwachen Backups und Wiederherstellung S3 storage, uploads and bulk backup actions Warnbenachrichtigungen (E-Mail und SMS)

Workspaces & Permissions

Workspace-Mitglieder einladen Mitgliederberechtigungen und Ressourcenzugriff Ein Mitglied kann eine Ressource nicht sehen oder nutzen Audit log and server activity

Account & Security

Zwei-Faktor-Authentifizierung (2FA) Profil- und Integrationseinstellungen Passwörter und Kontowiederherstellung

Billing & Plans

Tarife und Preise Dein Abonnement upgraden und verwalten Wenn ein Projekt-Abonnement unbezahlt bleibt Das Channel-Partner-Programm Onboarding a client as a partner

Support & Tickets

Ein Support-Ticket eröffnen Hilfe vom CICDoo-Team erhalten

Troubleshooting

Fehlerbehebung: Server kann nicht verbunden werden Fehlerbehebung: ein Deployment ist fehlgeschlagen Fehlerbehebung: git push schlägt mit 403 fehl nach Verschieben eines Repositorys Fehlerbehebung: meine Instanz ist ausgefallen oder langsam Fehlerbehebung: Domain- oder SSL-Probleme

Projekte & 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.

Zurück GitHub verbinden Weiter GitLab verbinden

Kommst du nicht weiter? Erstelle ein Ticket in der App oder sprich mit einem Techniker.