4 posts tagged with "Deployment"

Source Push integrates with your existing CI/CD tools to automate OTA releases. A typical pipeline might look like this:

# Build your app
npm run build

# Release to staging
srcpush release MyApp Staging ./build --description "Staging build"

# Promote to production after tests pass
srcpush promote MyApp Staging Production

This workflow ensures your updates are tested and approved before reaching end users.

When you're ready to move from testing to production, Source Push simplifies the process. Make sure to:

1. Use separate Staging and Production deployments
2. Test updates thoroughly in staging
3. Monitor metrics closely after the first production release

Following these steps helps ensure a smooth experience for your users when you switch to OTA updates with Source Push.

Even with thorough testing, issues can slip into production. Source Push provides easy rollback commands so you can revert to a previous release:

srcpush release rollback MyApp Production

You can also configure automatic rollbacks based on crash thresholds or custom metrics, giving your team peace of mind when shipping updates.

Deploying updates to your React Native app requires careful planning and execution. In this guide, we'll explore different deployment strategies available with Source Push and when to use them.

Understanding Deployment Environments​

Source Push supports multiple deployment environments out of the box:

# Create staging and production deployments
srcpush deployment add MyApp Staging
srcpush deployment add MyApp Production

This allows you to test updates before rolling them out to all users.

Staged Rollouts​

Staged rollouts help minimize the impact of potential issues by gradually releasing updates to users:

# Release to 25% of users initially
srcpush release-react MyApp ios --rollout 25

# Once confident, increase to 100%
srcpush deployment history MyApp Production
srcpush rollout MyApp Production v5 100

A/B Testing​

Test different versions of your app with specific user segments:

# Release version A
srcpush release-react MyApp ios -d Production-A

# Release version B
srcpush release-react MyApp ios -d Production-B

Automatic Rollbacks​

Source Push includes automatic rollback protection:

srcpush release-react MyApp ios --rollback-enabled true

This will automatically roll back if an update causes crashes above your defined threshold.

Best Practices​

1. Always Test in Staging

   srcpush release-react MyApp ios -d Staging
   # Verify in staging before promoting
   srcpush promote MyApp Staging Production
   

2. Monitor Update Metrics

   • Track download success rates
   • Monitor crash reports
   • Watch adoption rates

3. Version Targeting

   srcpush release-react MyApp ios --target-binary-version "~1.2.3"
   

4. Emergency Updates

   srcpush release-react MyApp ios --mandatory true
   

CI/CD Integration​

Automate your deployments with our CI/CD integrations:

# GitHub Actions example
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Install Source Push CLI
        run: npm install -g @srcpush/code-push-cli
      - name: Release Update
        run: srcpush release-react MyApp ios -d Staging
        env:
          SRCPUSH_TOKEN: ${{ secrets.SRCPUSH_TOKEN }}

Monitoring Deployments​

Keep track of your deployments using our monitoring tools:

# Check deployment history
srcpush deployment history MyApp Production

# View specific deployment details
srcpush deployment info MyApp Production

Conclusion​

Effective deployment strategies are crucial for maintaining app stability and user satisfaction. Source Push provides all the tools you need to implement sophisticated deployment workflows that match your team's needs.

For more detailed information, check out our deployment documentation and CI/CD integration guides.