All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and charts Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access SSH access to instances Instance settings explained Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problems

Projects & Git

Connecting GitHub

How to connect your GitHub account to CICDoo with OAuth or a classic token, why Enterprise needs a classic token, and how to disconnect.

CICDoo needs access to your GitHub account to create repositories, import existing ones and deploy them. You can connect in two ways:

  • OAuth: you approve CICDoo on GitHub and are sent back. This is the quickest way.
  • Classic token: you create a GitHub classic token with the repo and read:user scopes and paste it into CICDoo. A classic token authenticates as you, so it needs no OAuth app approval from your organization. Use it when your organization does not allow granting access to OAuth apps.

You manage the connection in Settings, on the "Integrations" tab, in the "GitHub Integration" card. The same options appear inside the "Create New Project" wizard when you pick GitHub, so you can connect without leaving it.

Connecting with OAuth

  1. Open Settings and go to the "Integrations" tab.
  2. In the "GitHub Integration" card, click "Connect with GitHub OAuth" (in the project wizard the button is "Connect with GitHub").
  3. Approve the request on GitHub.
  4. Back in CICDoo, check that the card shows "GitHub Connected" with your GitHub username.

Connecting with a classic token

  1. On GitHub, create a classic token with the repo and read:user scopes. The "GitHub Settings" link under the token field opens the right GitHub page with these scopes selected.
  2. In CICDoo, open Settings, go to the "Integrations" tab and, in the "GitHub Integration" card, click "use a classic token instead".
  3. Paste the token into "GitHub Classic Token".
  4. Click "Save token".
  5. Check that the card shows "GitHub Connected".

The token is stored on the platform and used to clone your repositories.

Enterprise edition needs a classic token

Odoo Enterprise repositories are private, and only a classic token can reach them. Projects on Enterprise need a GitHub classic token from an account that has access to the Odoo Enterprise repositories, even if you connected with OAuth. The "Integrations" tab shows an "Enterprise Edition Requires a Classic Token" notice with your current status:

  • "Classic token configured - ready for Enterprise edition": nothing to do.
  • "OAuth token detected, but a classic token is required for Enterprise": you connected with OAuth only.
  • "Classic token required for Enterprise edition": no token at all yet.

To add the token:

  1. In the "Enterprise Edition Requires a Classic Token" notice, click "Configure a classic token".
  2. Paste the token into "GitHub Classic Token".
  3. Click "Save token".

See Odoo versions and editions (Community vs Enterprise).

Using a different token for one project

A project can use its own classic token, for example when its repository lives in another organization. This is set per project on the GitHub tab of the project settings. See Project GitHub settings and webhook.

Disconnecting GitHub

  1. Open Settings and go to the "Integrations" tab.
  2. In the "GitHub Integration" card, click "Disconnect".
  3. Confirm the prompt.

You can reconnect at any time with OAuth or a new classic token. The same "Disconnect" button also appears in the project wizard when GitHub is connected.

If you moved or renamed the repository

If you transfer the repository to an organization or rename it on GitHub, fetches keep working but pushes start failing with a 403. Open the project settings, go to the GitHub tab and click "Re-sync from GitHub". See Troubleshooting: git push fails with 403 after moving a repository.

Related: Creating a project, Connecting GitLab, Profile and integrations settings, Project GitHub settings and webhook.

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

Previous Creating a project Next Project GitHub settings and webhook

Still stuck? Open a ticket from the app or talk to an engineer.