- Getting Started
- Example deployment to Heroku
- Using pipelines
- Deploying with Snap
- How do I add SSH keys to my build?
- Scheduling and skipping builds
- Deleting or cancelling a build run
- Billing owner best practices
- Deployment Pipeline
- The CI Environment
- Snap CI's Stacks
- Simple Docker pipeline using Snap CI
- Building & propagating Docker images
- Deploying Docker images
- Docker FAQ
- Known Limitations
- Relational Databases
- NoSQL Datastores
- Testing with browsers
- Complete Package List
- Environment Variables
- Heroku Deployments
- Deploying to AWS
- Deploying to AWS OpsWorks
- Deploying to AWS S3
- Deploying to AWS ElasticBeanstalk
- Working with Branches
- Cloning a pipeline
- Integration pipelines
- Automatic branch tracking
- Pull Requests
- Configuring multiple workers
- Speeding up builds
- Setting up test parallelism
- Pipeline Parallelism
- Polling project status using CCTray
- Webhook notifications
- How Snap integrates with GitHub
- Revoking privileges granted to Snap CI
- Managing membership
- Triggering Pipelines and Stages
- Migration to GoCD
- Migration to other CI and CD tools
Snap offers you the ability to diagnose a build, and making it a lot more straightforward.
If you’re having trouble with your build - just type
snap-shell as a command in your pipeline configuration.
snap-shell is active you'll see a terminal icon:
You can find more details on our blog post.
At this time is not possible to run
snap-shellin stages with multiple workers.
Debugging a stage failure
Sometimes you want to quickly investigate a stage failure. Changing the configuration and having a whole pipeline run can be cumbersome. Snap provides a stage debug rerun functionality which aims to help solve these issues.
When a stage fails you'll see at the bottom left of the stage a bug icon:
Clicking on this icon will rerun the stage in debug mode. In this mode Snap
will automatically invoke
snap-shell if a task fails, giving you a chance to
investigate the problem.