GitLab CI/CD

将 Capgo Live Updates 与 GitLab CI/CD 集成，以便在推送 code 更改时自动部署您的应用程序更新。 本指南涵盖了设置自动构建、测试和部署工作流程。

先决条件

在设置 GitLab CI/CD 集成之前，请确保您有：

• 一个 GitLab 帐户和一个项目仓库
• 一个 Capgo 帐户和一个已配置的应用
• Node.js 和 npm/yarn 在项目中配置

设置 GitLab CI/CD

步骤 1：配置环境变量

首先，在您的 GitLab 项目中设置必要的变量：

1. 前往您的 GitLab 项目
2. 前往 设置 → CI/CD → 变量
3. 添加以下变量：

变量名称	值	受保护	掩码
CAPGO_TOKEN	您的 Capgo API token	✅ 是	✅ 是

提示

Get your Capgo API token from console.capgo.app/apikeys您的应用 ID 已经在您的 capacitor.config.ts 文件中配置

简单

基本配置，生产环境每次推送主分支:

# .gitlab-ci.yml - Simple Configuration
image: node:22

stages:
  - build
  - deploy

variables:
  npm_config_cache: "$CI_PROJECT_DIR/.npm"

build:
  stage: build
  script:
    - npm ci
    - npm run test
    - npm run build
  artifacts:
    paths:
      - dist/
    expire_in: 1 hour
  only:
    - main

deploy_production:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production
    # For encrypted uploads, add: --key-data-v2 "$CAPGO_PRIVATE_KEY"
  dependencies:
    - build
  only:
    - main

高级

特性分支部署

将特性分支部署到测试频道进行审查和测试:

# Feature branch deployment
deploy_feature:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - CHANNEL_NAME="feature-$(echo $CI_COMMIT_REF_NAME | sed 's/[^a-zA-Z0-9-]/-/g')"
    - npx @capgo/cli channel create $CHANNEL_NAME --apikey $CAPGO_TOKEN || true
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME
  dependencies:
    - build
  only:
    - /^feature\/.*$/
  environment:
    name: feature/$CI_COMMIT_REF_NAME
    url: https://your-app.com/channels/$CHANNEL_NAME

提示

使用频道进行测试: 在将应用程序部署到特性频道后，您可以通过配置应用程序使用特定频道来测试更新。了解有关配置频道的更多信息。 配置频道.

使用加密

如果您正在使用 Capgo的加密功能,则需要在CI/CD环境中安全存储您的私钥。

在 设置加密密钥 本地后，

# Display your private key content (copy this output)
cat .capgo_key_v2

添加此内容作为 CAPGO_PRIVATE_KEY 在您的 GitLab 项目变量中（标记为受保护并加密），然后在管道中使用它：

# Deploy with encryption
deploy_production:
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --key-data-v2 "$CAPGO_PRIVATE_KEY" --channel production

注意

安全最佳实践：

• 永远不要将 .capgo_key_v2 文件提交到版本控制
• 仅在安全的 CI/CD 秘密管理中存储私钥
• 为不同环境使用不同的密钥

多渠道配置

关于设置和管理多个发布渠道的详细信息，请参见 Channels 文档.

多环境和合并请求部署的完整配置：

# .gitlab-ci.yml - Advanced Multi-Channel Configuration
image: node:22

stages:
  - build
  - deploy

variables:
  npm_config_cache: "$CI_PROJECT_DIR/.npm"

# Build stage
build:
  stage: build
  script:
    - npm ci
    - npm run test
    - npm run build
  artifacts:
    paths:
      - dist/
    expire_in: 24 hours

# Deploy to development channel
deploy_development:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel development
  dependencies:
    - build
  only:
    - develop
  environment:
    name: development

# Deploy merge requests to test channels
deploy_mr:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - CHANNEL_NAME="mr-$CI_MERGE_REQUEST_IID"
    - npx @capgo/cli channel create $CHANNEL_NAME --apikey $CAPGO_TOKEN || true
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME
  dependencies:
    - build
  only:
    - merge_requests
  environment:
    name: review/$CI_MERGE_REQUEST_IID
    url: https://your-app.com/channels/mr-$CI_MERGE_REQUEST_IID
    on_stop: cleanup_mr

# Cleanup MR channels when MR is closed
cleanup_mr:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli channel delete mr-$CI_MERGE_REQUEST_IID --apikey $CAPGO_TOKEN || true
  when: manual
  environment:
    name: review/$CI_MERGE_REQUEST_IID
    action: stop
  only:
    - merge_requests

# Deploy to staging
deploy_staging:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel staging
  dependencies:
    - build
  only:
    - develop
  environment:
    name: staging

# Deploy to production
deploy_production:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production
  dependencies:
    - build
  only:
    - main
  environment:
    name: production

需要手动审批的生产部署：

Branch-Based 部署策略

deploy_production:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production
  dependencies:
    - build
  only:
    - main
  when: manual
  environment:
    name: production

自动将不同分支部署到适当的渠道：

Section titled “Multi-Environment with Manual Approval”

# Dynamic channel deployment based on branch
deploy:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - |
      if [ "$CI_COMMIT_REF_NAME" = "main" ]; then
        CHANNEL="production"
      elif [ "$CI_COMMIT_REF_NAME" = "develop" ]; then
        CHANNEL="staging"
      else
        CHANNEL="development"
      fi
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL
  dependencies:
    - build
  environment:
    name: $CHANNEL

安全最佳实践

保护变量

1. 标记敏感变量: 总是将 API 标记为保护和掩码
2. 分支保护: 使用保护变量进行生产部署
3. 访问控制: 限制变量访问仅限维护人员
4. 定期轮换: 定期轮换 API 变量

安全管道配置

# Use protected variables for production
deploy_production:
  stage: deploy
  script:
    - npm install -g @capgo/cli
    - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production
  only:
    refs:
      - main
    variables:
      - $CI_COMMIT_REF_PROTECTED == "true"

监控和通知

Slack 集成

将 Slack 通知添加到管道：

notify_success:
  stage: .post
  image: alpine:latest
  before_script:
    - apk add --no-cache curl
  script:
    - |
      curl -X POST -H 'Content-type: application/json' \
        --data '{"text":"✅ Capgo deployment successful for '"$CI_COMMIT_REF_NAME"'"}' \
        $SLACK_WEBHOOK_URL
  when: on_success

notify_failure:
  stage: .post
  image: alpine:latest
  before_script:
    - apk add --no-cache curl
  script:
    - |
      curl -X POST -H 'Content-type: application/json' \
        --data '{"text":"❌ Capgo deployment failed for '"$CI_COMMIT_REF_NAME"'"}' \
        $SLACK_WEBHOOK_URL
  when: on_failure

电子邮件通知

在您的 GitLab 项目设置中配置电子邮件通知或使用 API:

notify_email:
  stage: .post
  script:
    - |
      curl --request POST \
        --header "PRIVATE-TOKEN: $GITLAB_API_TOKEN" \
        --form "to=team@yourcompany.com" \
        --form "subject=Capgo Deployment Status" \
        --form "body=Deployment of $CI_COMMIT_REF_NAME completed with status: $CI_JOB_STATUS" \
        "https://gitlab.com/api/v4/projects/$CI_PROJECT_ID/emails"
  when: always

故障排除

故障排除

Pipeline fails with “Capgo CLI not found”:

# Debug CLI installation
debug_cli:
  script:
    - npm install -g @capgo/cli
    - which capgo || echo "Capgo CLI not found"
    - npx @capgo/cli --version

复制到剪贴板

# Verify token configuration
debug_auth:
  script:
    - |
      if [ -z "$CAPGO_TOKEN" ]; then
        echo "CAPGO_TOKEN is not set"
        exit 1
      fi
      echo "Token length: ${#CAPGO_TOKEN}"

复制到剪贴板

# List build outputs
debug_build:
  script:
    - ls -la dist/
    - find dist/ -type f -name "*.js" -o -name "*.html"

复制到剪贴板

添加调试信息以解决问题:

debug:
  stage: build
  script:
    - echo "Branch: $CI_COMMIT_REF_NAME"
    - echo "Commit: $CI_COMMIT_SHA"
    - echo "Build: $CI_PIPELINE_ID"
    - env | grep CI_ | sort
  only:
    - branches

下一步

• 了解 频道 管理不同部署环境
• 探索 自定义存储 用于高级部署场景
• 设置 加密 确保安全的部署
• 配置 更新行为 以自定义方式应用更新

With GitLab CI/CD integration, you can automate your Capgo deployments and ensure consistent, reliable updates to your mobile app users.

继续使用 GitLab CI/CD 集成

如果您正在使用 GitLab CI/CD 集成 来规划 CI/CD 自动化，连接它与 Capgo CI/CD 为Capgo CI/CD产品工作流程 Capgo 原生构建 为Capgo 原生构建产品工作流程 Capgo 集成 为Capgo 集成产品工作流程 CI/CD 集成 为CI/CD 集成的实现细节 GitHub 动作集成 为GitHub 动作集成的实现细节