Git Providers Overview

ButterStack supports multiple Git providers with full integration capabilities. Choose the provider that matches your repository host.

Table of contents

1. Supported Git Providers
   1. GitHub Integration
   2. GitLab Integration
   3. Bitbucket Integration
2. Common Features
   1. Commit Tracking
   2. Task Linking
   3. Build Triggering
   4. Real-time Updates
3. Choosing a Provider
4. Setup Process
5. Migration Between Providers
   1. Moving from GitHub to GitLab
   2. Moving from GitLab to Bitbucket
   3. Preserving History
6. Security Best Practices
7. Troubleshooting
   1. Common Issues Across Providers
8. Advanced Configuration
   1. Multi-Repository Setup
   2. Branch Filtering
   3. Custom Workflows
9. Next Steps
10. Need Help?
11. Related

Supported Git Providers

ButterStack provides native integrations for major Git hosting providers. Each integration offers the same core functionality with provider-specific optimizations.

GitHub Integration

Full Support Available

• Repository monitoring via GitHub API
• Webhook integration for real-time updates
• GitHub Actions workflow integration
• Branch and pull request tracking
• Issue linking via commit messages

Set up GitHub Integration →

GitLab Integration

Full Support Available

• GitLab.com and self-hosted instances
• Merge request tracking
• GitLab CI integration capabilities
• Project access token authentication
• Webhook event handling

Set up GitLab Integration →

Bitbucket Integration

Full Support Available

• Bitbucket Cloud and Bitbucket Server
• Pull request monitoring
• App password authentication
• Branch and commit tracking
• Webhook notifications

Set up Bitbucket Integration →

Common Features

All Git provider integrations support:

Commit Tracking

• Automatic commit monitoring
• File change detection
• Author identification
• Branch associations

Task Linking

Include task references in commit messages:

PROJ-123: Updated character textures

- Improved resolution on hero mesh
- Fixed UV mapping issues

Build Triggering

Use commit tags to trigger automated builds:

• #ci - Trigger default build
• #build - Trigger default build
• #jenkins:JobName - Trigger specific job

Real-time Updates

• Webhook integration for instant notifications
• Automatic sync on push/merge events
• Branch and tag monitoring

Choosing a Provider

Setup Process

The setup process is similar across all providers:

1. Generate credentials (token/app password)
2. Add integration in ButterStack project settings
3. Test connection to verify access
4. Configure webhook for real-time updates (optional)
5. Set up build triggers in your CI/CD system

Migration Between Providers

Moving from GitHub to GitLab

• Update repository URLs in ButterStack
• Generate GitLab access token
• Reconfigure webhook endpoints
• Update CI/CD integration references

Moving from GitLab to Bitbucket

• Configure Bitbucket app password
• Update repository URLs and webhook configuration
• Adjust branch naming if different
• Review API rate limits (vary by provider)

Preserving History

ButterStack maintains historical data when switching providers:

• Previous commits remain linked to builds
• Asset lineage history is preserved
• Integration logs are retained

Security Best Practices

Regardless of provider:

1. Minimal Permissions: Grant only required repository access
2. Token Rotation: Regularly rotate access credentials
3. Webhook Security: Use HTTPS and verify signatures
4. Network Security: Allowlist ButterStack IPs if required
5. Audit Logs: Monitor integration access logs

Troubleshooting

Common Issues Across Providers

Authentication Failures

• Verify token/password hasn’t expired
• Check repository access permissions
• Ensure correct scopes are granted

Webhook Delivery Problems

• Confirm webhook URL and token are correct
• Check delivery logs in provider settings
• Verify ButterStack webhook logs

Missing Commits

• Verify branch monitoring configuration
• Check if commits are on tracked branches
• Review webhook event configuration

Advanced Configuration

Multi-Repository Setup

• Add separate integrations for each repository
• Configure different webhook endpoints
• Set repository-specific build triggers

Branch Filtering

• Monitor only specific branches (main, develop, release/*)
• Ignore feature branches or personal forks
• Configure different behavior per branch type

Custom Workflows

• Set up different build triggers per repository
• Configure repository-specific notifications
• Customize asset tracking rules

Next Steps

After setting up your Git integration:

1. Configure Jenkins Integration - Set up automated builds
2. Add Task Management - Link commits to project tasks
3. Enable Notifications - Keep your team informed
4. Set Up Asset Pipeline - Complete the asset lineage

Need Help?

• Provider-Specific Guides: See individual integration pages for detailed setup
• Support: support@butterstack.com
• Community: Join our Discord

Related

• GitHub Integration - GitHub-specific setup guide
• GitLab Integration - GitLab-specific configuration
• Bitbucket Integration - Bitbucket setup instructions
• Core Concepts: 5-Stage Pipeline - Understanding asset lineage