Semaphore CI vs Snap CI

Whenever a new push is made on GitHub or Bitbucket, Semaphore automatically runs tests on that branch.

Semaphore supports open source and offers unlimited open source projects.

Semaphore offers all-around customer support for its commercial users.

Semaphore offers 100 builds every month for private projects. This package is free for an unlimited time and offers: free & unlimited deploys, unlimited collaborators and running tests in parallel.

Projects can be imported from GitHub and Semaphore will automatically connect with that repository, once that's done, it will automatically trigger for every code commit.

Out of the box Docker support. Additionally, Semaphore can cache Docker images by using included docker-cache commands.

Semaphore is quite easy to configure and work with. It easily integrates with GitHub and a first build is only a few clicks away.

Semaphore is configured using .yaml configuration files which can be added from the web UI. There are a lot of tutorials out there that help developers configure Semaphore to their preference.

Snap CI keeps the build history of a branch for as long as that branch is active. Once it's deleted or merged it is automatically deleted.

Deployments are configured to run in sequence, one after one in the build pipeline. Not every environment is updated on every change, this is especially helpful for example for someone who is testing the application and does not want their environment to change while they are doing it.

Snap watches for pull requests on a repository that it's building and automatically issues a pipeline, attempts to merge the pull-request and finally run the pipeline.

Interactive tutorials explain how to set up an configure pipelines quickly and easily.
Sane defaults provided for testing and deployment stages.

Artifacts are manually generated and propagated through the deployment pipeline.

Snap offers developers a simple and easy to use tool for debugging their applications. Just by typing snap-shell on their pipeline configuration they will have the ability to visit their logs page where they can start debugging. The log page shows a command prompt with some help on how to use it.

Very responsive and personal support in addition to automated responders.

Snap watches for any new branch that is created and once it catches one of these new branches, if the master branch is configured for a pipeline it will create a new pipeline around the new branch. Once the branch is deleted or merged with master, the newly created pipeline is deleted by Snap

Snap's build pipeline guarantees that the exact same set of git commits trigger each stage.