全部文章

Getting Started

什么是 CICDoo 快速开始: 引导向导 仪表盘与基础设施地图

Concepts

生产、预发布和开发阶段 域名、子域名和 SSL Odoo 版本与版本类型（Community 与 Enterprise） 工作区与团队协作

Servers

添加服务器 服务器域名与 DNS 使用负载均衡器 服务器操作: 部署、日志与图表 Deleting a server

Projects & Git

创建项目 连接 GitHub Project GitHub settings and webhook 连接 GitLab 分支与实例 为项目添加标签和筛选项目 使用应用节点实现高可用性 Project environments, extensions and deletion

Instances & Console

创建实例 重启、停止和删除实例 在阶段之间合并分支 Web IDE 与远程访问 SSH access to instances 实例设置详解 部署与任务队列

Agent Tasks

什么是智能体任务 设置智能体任务 运行任务并查看结果 智能体时间与充值 Agent insights and task filters

Monitoring & Backups

监控你的实例 备份与恢复 S3 storage, uploads and bulk backup actions 告警通知（邮件与短信）

Workspaces & Permissions

邀请工作区成员 成员权限与资源访问 成员看不到或无法使用某个资源 Audit log and server activity

Account & Security

双重验证（2FA） 个人资料与集成设置 密码与账户找回

Billing & Plans

方案与价格 升级和管理订阅 项目订阅未支付时 渠道合作伙伴计划 Onboarding a client as a partner

Support & Tickets

提交支持工单 获取 CICDoo 团队的帮助

Troubleshooting

故障排查: 无法连接服务器 故障排查: 部署失败 故障排查: 迁移仓库后 git push 返回 403 故障排查: 实例宕机或变慢 故障排查: 域名或 SSL 问题

项目与 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.

上一篇 连接 GitHub 下一篇 连接 GitLab

仍未解决？在应用中提交工单，或与工程师沟通。