메뉴로 이동

Bitbucket PIPELINE 통합

Bitbucket Pipelines와 함께 Capgo Live Updates를 통합하여 code 변경 사항을 푸시할 때마다 자동으로 앱 업데이트를 배포하세요. 이 가이드에서는 자동화된 빌드, 테스트, 및 배포 워크플로우를 설정하는 방법을 설명합니다.

사전 요구 사항

사전 요구 사항 제목

Bitbucket Pipelines 통합을 설정하기 전에 다음을 확인하세요:

  • Bitbucket 계정과 저장소가 있는 경우
  • Capgo 계정에 앱이 설정된
  • npm와 Node.js/yarn이 프로젝트에 설정된

Bitbucket Pipelines 설정

Bitbucket Pipelines 설정

1단계: 저장소 변수 설정

1단계: 저장소 변수 설정

먼저, Bitbucket 저장소에서 필요한 변수를 설정하세요.

  1. Bitbucket 저장소로 이동하세요.
  2. Go to 저장소 설정 Pipelines저장소 변수
  3. __CAPGO_KEEP_0__ __CAPGO_KEEP_1__ 변수를 추가하세요:
변수 이름보안
CAPGO_TOKENCapgo API 토큰을 얻으세요✅ 예

기본 설정: 매 주 main branch에 푸시될 때마다 프로덕션으로 배포합니다.

# bitbucket-pipelines.yml - Simple Configuration
image: 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/**

Advanced

고급

클립보드에 복사

# Feature branch deployment
pipelines:
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_KEEP_0__의 암호화 기능을 사용하고 있다면, CI/CD 환경에서 개인 키를 안전하게 저장해야 합니다. Capgo’s encryption feature터미널 창

__CAPGO_KEEP_0__ __CAPGO_KEEP_0__ __CAPGO_KEEP_0__

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

이 콘텐츠를 CAPGO_PRIVATE_KEY Bitbucket 저장소 변수에 추가하세요 (보안 표시). 그런 다음 pipeline에서 사용하세요:

# 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

멀티 채널 구성

Multi-Channel Configuration

Multi-Channel Configuration Multi-Channel Configuration.

Channels 문서를 참조하십시오.

# bitbucket-pipelines.yml - Advanced Multi-Channel Configuration
image: 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/**

Multi-Environment Pipeline

# Multi-environment pipeline
image: 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/**

Branch-Based Deployment Strategy

Branch-Based Deployment Strategy

Branch-Based Deployment Strategy

# Dynamic channel deployment
image: 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/**

병렬 pipe 라인 실행

병렬 pipe 라인 실행 섹션

병렬 단계를 사용하여 빌드 시간을 최적화하세요.

# Parallel execution pipeline
image: 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

보안 최적화

보안 최적화 섹션

저장소 변수

저장소 변수 섹션
  1. 보안 변수API 항상 API 토큰을 보안 변수로 표시하세요.
  2. 환경 변수__CAPGO_KEEP_0__ __CAPGO_KEEP_1__를 필요할 때만 배포 특정 변수를 사용하십시오.
  3. 권한 관리: 권한이 있는 팀 구성원만에 대한 저장소 접근을 제한하십시오.
  4. 토큰 회전: 정기적으로 Capgo API 토큰을 회전하십시오.

배포 환경을 더 안전하게 하기 위해 설정하십시오.

# Deployment with environment restrictions
pipelines:
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 통합

pipeline에 Slack 알림을 추가하세요:

# Pipeline with Slack notifications
pipelines:
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 fails with “Capgo CLI not found”:

# 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"

디버그 PIPELINE

디버그 PIPELINE 섹션

문제를 해결하기 위해 디버깅 정보를 추가합니다.

# Debug pipeline
pipelines:
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

PIPELINE VALIDATION

PIPELINE VALIDATION 섹션

설정 오류를 잡기 위해 PIPELINE VALIDATION을 활성화합니다.

# Enable pipeline validation
options:
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 통합에서 계속 진행하기

Bitbucket Pipelines 통합에서 계속 진행하기

Bitbucket Pipelines 통합을 사용 중이면 Bitbucket Pipelines 통합 CI/CD 자동화 계획을 위해 Bitbucket Pipelines 통합을 연결하고 Capgo CI/CD Capgo CI/CD에서 제품 워크플로우 Capgo 네이티브 빌드 제품 워크플로우에서 Capgo 네이티브 빌드에 대해 Capgo 통합 Capgo 통합에 대해 제품 워크플로우 CI/CD 통합 CI/CD 통합에 대한 구현 세부 정보, 및 GitHub 액션 통합에 대해 구현 세부 정보 for the implementation detail in GitHub Actions Integration.