Bitbucket Pipelines 集成
复制一个包含安装步骤和此插件的完整Markdown指南的设置提示。
与 Bitbucket Pipelines 集成 Capgo 实时更新,以便每当您推送 code 变更时,自动部署您的应用程序更新。这份指南涵盖了设置自动构建、测试和部署工作流程。
前置条件
标题为“前置条件”在设置 Bitbucket Pipelines 集成之前,请确保您有:
- 一个 Bitbucket 帐户和一个仓库
- 一个 Capgo 帐户和已配置的应用
- Node.js 和 npm/yarn 已在您的项目中配置
设置 Bitbucket Pipelines
设置 Bitbucket Pipelines步骤 1:配置存储库变量
步骤 1:配置存储库变量首先,在您的 Bitbucket 存储库中设置必要的变量:
- 前往您的 Bitbucket 存储库
- 前往 存储库设置 → 管道 → 存储库变量
- 添加以下变量:
| 变量名 | 值 | 已加密 |
|---|---|---|
CAPGO_TOKEN | 您的 Capgo API token | ✅ 是 |
基本配置,自动部署到生产环境每次推送到主分支:
# bitbucket-pipelines.yml - Simple Configurationimage: node:22
pipelines: branches: main: - step: name: Build and Deploy to Production script: - npm ci - npm run test - npm run build - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production artifacts: - dist/**功能分支部署
Section titled “功能分支部署”将功能分支部署到测试频道进行审查和测试:
# Feature branch deploymentpipelines: branches: feature/*: - step: name: Deploy Feature Branch script: - npm ci - npm run test - npm run build - BRANCH_NAME=$(echo $BITBUCKET_BRANCH | sed 's/[^a-zA-Z0-9-]/-/g') - CHANNEL_NAME="feature-$BRANCH_NAME" - npm install -g @capgo/cli - npx @capgo/cli channel create $CHANNEL_NAME --apikey $CAPGO_TOKEN || true - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME artifacts: - dist/**使用加密
标题为“使用加密”如果您正在使用 Capgo的加密功能,则需要在CI/CD环境中安全存储您的私钥。
在 设置加密密钥后 本地添加您的私钥到Bitbucket变量中:
# Display your private key content (copy this output)cat .capgo_key_v2在您的 Bitbucket 仓库变量中添加此内容(标记为安全),然后在管道中使用: CAPGO_PRIVATE_KEY 在您的 Bitbucket 仓库变量中添加此内容(标记为安全),然后在管道中使用:
# Deploy with encryption- step: name: Deploy to Capgo with Encryption script: - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --key-data-v2 "$CAPGO_PRIVATE_KEY" --channel production多渠道配置
多渠道配置有关设置和管理多个发布渠道的详细信息,请参阅 Channels 文档.
多环境和 pull request 部署:
# bitbucket-pipelines.yml - Advanced Multi-Channel Configurationimage: node:22
definitions: steps: - step: &build-step name: Build Application script: - npm ci - npm run test - npm run build artifacts: - dist/**
- step: &deploy-step name: Deploy to Capgo script: - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME
pipelines: branches: main: - step: <<: *build-step - step: <<: *deploy-step name: Deploy to Production deployment: production trigger: manual script: - export CHANNEL_NAME=production - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME
develop: - step: <<: *build-step - step: <<: *deploy-step name: Deploy to Development deployment: development script: - export CHANNEL_NAME=development - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME
pull-requests: '**': - step: <<: *build-step - step: name: Deploy PR to Test Channel script: - CHANNEL_NAME="pr-$BITBUCKET_PR_ID" - npm install -g @capgo/cli - npx @capgo/cli channel create $CHANNEL_NAME --apikey $CAPGO_TOKEN || true - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME artifacts: - dist/**多环境管道
关于“多环境管道”对于具有 staging 和生产环境的复杂部署场景:
# Multi-environment pipelineimage: node:22
pipelines: branches: main: - step: name: Build script: - npm ci - npm run test - npm run build artifacts: - dist/** - step: name: Deploy to Staging deployment: staging script: - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel staging - step: name: Deploy to Production deployment: production trigger: manual script: - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production
develop: - step: name: Build and Deploy to Development script: - npm ci - npm run test - npm run build - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel development artifacts: - dist/**分支部署策略
关于“分支部署策略”自动将不同分支部署到适当的渠道:
# Dynamic channel deploymentimage: node:22
definitions: scripts: - script: &determine-channel | if [ "$BITBUCKET_BRANCH" = "main" ]; then export CHANNEL_NAME="production" elif [ "$BITBUCKET_BRANCH" = "develop" ]; then export CHANNEL_NAME="staging" else export CHANNEL_NAME="development" fi echo "Deploying to channel: $CHANNEL_NAME"
pipelines: default: - step: name: Build and Deploy script: - npm ci - npm run test - npm run build - *determine-channel - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel $CHANNEL_NAME artifacts: - dist/**并行管道执行
并行管道执行部分通过并行步骤优化构建时间:
# Parallel execution pipelineimage: node:22
pipelines: branches: main: - parallel: - step: name: Run Tests script: - npm ci - npm run test - step: name: Lint Code script: - npm ci - npm run lint - step: name: Build Application script: - npm ci - npm run build artifacts: - dist/** - step: name: Deploy to Production deployment: production script: - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production安全最佳实践
安全最佳实践部分仓库变量
仓库变量部分- 安全变量始终将API标记为安全变量
- 环境变量使用需要的部署特定变量
- 访问控制:限制仓库访问给授权团队成员
- 令牌轮换:定期轮换您的CapgoAPI令牌
部署环境
部署环境部分配置部署环境以提高安全性:
# Deployment with environment restrictionspipelines: branches: main: - step: name: Deploy to Production deployment: production trigger: manual script: - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production监控和通知
监控和通知部分Slack 集成
Slack 集成部分在 pipeline 中添加 Slack 通知:
# Pipeline with Slack notificationspipelines: branches: main: - step: name: Build and Deploy script: - npm ci - npm run test - npm run build - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production after-script: - | if [ $BITBUCKET_EXIT_CODE -eq 0 ]; then curl -X POST -H 'Content-type: application/json' \ --data '{"text":"✅ Capgo deployment successful for '$BITBUCKET_BRANCH'"}' \ $SLACK_WEBHOOK_URL else curl -X POST -H 'Content-type: application/json' \ --data '{"text":"❌ Capgo deployment failed for '$BITBUCKET_BRANCH'"}' \ $SLACK_WEBHOOK_URL fi电子邮件通知
电子邮件通知部分通过 Bitbucket 内置功能或使用外部服务配置电子邮件通知:
# Email notification step- step: name: Send Notification script: - | curl -X POST \ -H "Content-Type: application/json" \ -d '{ "to": "team@yourcompany.com", "subject": "Capgo Deployment Status", "body": "Deployment of '$BITBUCKET_BRANCH' completed with status: '$BITBUCKET_EXIT_CODE'" }' \ $EMAIL_SERVICE_URL condition: result: [successful, failed]故障排除
故障排除部分常见问题
故障排除部分常见问题pipeline 失败时显示“Capgo CLI 未找到”:
# Debug CLI installation- step: name: Debug CLI script: - npm install -g @capgo/cli - which capgo || echo "Capgo CLI not found" - npx @capgo/cli --version认证错误:
# Verify token configuration- step: name: 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- step: name: Debug Build script: - ls -la dist/ - find dist/ -type f -name "*.js" -o -name "*.html"调试管道
调试管道添加调试信息以解决问题:
# Debug pipelinepipelines: branches: main: - step: name: Debug Information script: - echo "Branch: $BITBUCKET_BRANCH" - echo "Commit: $BITBUCKET_COMMIT" - echo "Build: $BITBUCKET_BUILD_NUMBER" - env | grep BITBUCKET_ | sort - step: name: Build and Deploy script: - npm ci - npm run test - npm run build - npm install -g @capgo/cli - npx @capgo/cli bundle upload --apikey $CAPGO_TOKEN --channel production管道验证
管道验证启用管道验证以捕获配置错误:
# Enable pipeline validationoptions: docker: true size: 2x
pipelines: branches: main: - step: name: Validate Pipeline script: - echo "Pipeline validation successful" - step: name: Build and Deploy script: # ... deployment steps下一步
名为“下一步”的部分通过 Bitbucket Pipelines 集成,您可以自动化您的 Capgo 部署并确保您的移动应用用户接收到一致可靠的更新。
从 Bitbucket Pipelines Integration 中继续
标题:从 Bitbucket Pipelines Integration 中继续如果您正在使用 Bitbucket Pipelines Integration 来规划 CI/CD 自动化,连接它与 Capgo CI/CD 来规划 Capgo CI/CD 的产品工作流程 Capgo Native Builds 来规划 Capgo Native Builds 的产品工作流程 Capgo 集成 为产品工作流程在 Capgo 集成中 CI/CD 集成 为 CI/CD 集成的实现细节 GitHub 动作集成 为 GitHub 动作集成的实现细节