Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
Shippable runs inside Docker containers. Docker has some specific security measures which may or may not become a hindrance in using Shippable. It may be harder for users who are not very comfortable with a Linux container environment and that can create some security problems. Even for more advanced users, it's still something more that they have to address while using Shippable. See More
Currently, Shippable does not allow for build artifacts to be natively deployed to S3. This can be gotten around, however it is a rather large hole when compared to Travis. In order to deploy to S3 you have to add a couple of lines to the yml file. For example: env: global: #secure variable contains values for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY - secure: HKwYujx/qmsyQQdHvR2myu8HLUDtcLeDyYV149YJuxIV4J7Hk3SxeY8X3D6aTlR8mvMnd/ZFY+tGNUh4G0xtLLjjZcPsBgvFlB build: on_success: - aws s3 sync $SHIPPABLE_BUILD_DIR "s3://bucket_name" --region "us-east-1" See More
Shippable is built using Docker, a popular open source Linux container. It was originally built using it's own container but when that started to become too complex, they switched to using Docker. Since the beginning Shippable was different from other CI tools because while Shippable uses a container (Docker), traditionally CI tools have used virtual machines to manage their workloads. See More
The fact that Shippable runs inside of Docker means that it keeps a persistent state and every build will not have to revert to initial state where it needs to install every dependency from the ground up. Classic CI tools that run on virtual machines need to reset their environment every time and every time install the gems, packages and services needed. See More
Bamboo is made by Atlassian, the company that also made and maintains tools such as JIRA, Stash and BitBucket, so it's a given that they would integrate quite nicely. For example, when connecting Bamboo with Stash and JIRA, details like JIRA issues, commits, reviews and approvals follow each release from development to production. If HipCHat is part of the integration, team members get notified right away in addition to email notifications. See More
While you can docker "run" "build" "exec" etc with bamboo and docker one key thing you will find you cannot do is to run your bamboo job inside a container. A job must manage the container setup and teardown, this can lead to left-over containers using memory or filesystem permissions issues if your container can run as root and leaves files behind in a mounted volume. If for example you want to run your bamboo agent in a fresh container for each build then you are out of luck and have to build this infrastructure yourself. See More
Bamboo is the only build server to offer first-class support for the "delivery" aspect of continuous delivery. Deployment projects automate the tedium right out of releasing into each environment, while letting you control the flow with per-environment permissions. See More
Bamboo allows using Docker containers to create build agents. Using Docker agents lets you run multiple remote agents on the same host without conflicting requirements. It makes it easier to duplicate and distribute changes to build agents, and to use scripts for creating and maintaining agents. How can you define and build your own image and push it to a registry to share?This is when Bamboo’s Docker tasks come into play. Docker tasks make it possible to build an image, run a container, and push a Docker image to a registry from within your build or deployment project. See More
Help millions of people make better decisions.
Each month, over 2.8 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.