Permalink
Browse files

Added copyright line to all files

  • Loading branch information...
suziejprince committed May 31, 2017
1 parent 6892a20 commit 79aefeeb658a7c54381e15a6bd7a128b8007ee91
Showing with 303 additions and 0 deletions.
  1. +3 −0 posts/2012-10-25-setting-up-a-build-server-is-so-2011.md
  2. +3 −0 posts/2012-11-27-enter-snap.md
  3. +3 −0 posts/2013-02-21-beyond-staging.md
  4. +3 −0 posts/2013-03-18-would-you-like-a-build-branch.md
  5. +3 −0 posts/2013-08-06-ci-does-include-deploying-to-production.md
  6. +3 −0 posts/2013-09-12-announcing-support-for-some-no-sql-databases.md
  7. +3 −0 posts/2013-09-13-heroku-oauth.md
  8. +3 −0 posts/2013-09-18-dropwizard-deployment-pipeline.md
  9. +3 −0 posts/2013-10-01-scala-play-build-on-snap-ci.md
  10. +3 −0 posts/2013-10-21-aws-elastic-beanstalk.md
  11. +3 −0 posts/2013-11-07-automatic-branch-tracking-and-integration.md
  12. +3 −0 posts/2013-11-18-local-rails-development-with-service-stubs.md
  13. +3 −0 posts/2014-04-10-snap-heartbleed-security-advisory.md
  14. +3 −0 posts/2014-04-17-deploy-demand-rubygems.md
  15. +3 −0 posts/2014-07-22-why-snapci-and-travisci-are-not-same-thing.md
  16. +3 −0 posts/2014-08-01-introducing-snap-shell.md
  17. +3 −0 posts/2014-09-12-pull-request-integration.md
  18. +3 −0 posts/2014-09-23-building-clojure-projects-on-snap.md
  19. +3 −0 posts/2014-09-26-snap-bash-vulnerability-advisory.md
  20. +3 −0 posts/2014-10-15-aws-opsworks.md
  21. +3 −0 posts/2014-10-17-aws-elastic-beanstalk-revisited.md
  22. +3 −0 posts/2014-11-04-shell-changes.md
  23. +3 −0 posts/2014-11-25-openshift-deployments.md
  24. +3 −0 posts/2014-12-19-faster-builds-multiple-workers.md
  25. +3 −0 posts/2015-02-13-faster-builds-workers.md
  26. +3 −0 posts/2015-02-23-notification-center-deliberate-approach.md
  27. +3 −0 posts/2015-03-16-meet-fernando-junior.md
  28. +3 −0 posts/2015-03-17-AirPair-Dev-Writing-Competition.md
  29. +3 −0 posts/2015-03-18-rbenv-and-upcoming-nvm-changes.md
  30. +3 −0 posts/2015-04-03-blue-green-deployments.md
  31. +3 −0 posts/2015-04-06-canary-releases.md
  32. +3 −0 posts/2015-04-14-continuous-delivery-journey.md
  33. +3 −0 posts/2015-06-22-continuous-deployment-strategies.md
  34. +3 −0 posts/2015-07-23-multi-stage-builds.md
  35. +3 −0 posts/2015-07-31-global-environment-variables.md
  36. +3 −0 posts/2015-08-05-how-snapci-sets-up-build-env.md
  37. +3 −0 posts/2015-08-12-types-of-containers.md
  38. +3 −0 posts/2015-08-18-canary-release-helped-delivery-rails-upgrade.md
  39. +3 −0 posts/2015-09-09-snap-container-security.md
  40. +3 −0 posts/2015-09-22-pull-request-workflow.md
  41. +3 −0 posts/2015-09-30-snap-ci-api-ifttt-fun.md
  42. +3 −0 posts/2015-10-06-enabling-trunk-based-development.md
  43. +3 −0 posts/2015-10-15-does-snap-go-press-release.md
  44. +3 −0 posts/2015-10-28-playing-websockets-fun-profit-debugging-remote-machines.md
  45. +3 −0 posts/2015-11-09-long-multi-stage-pipeline.md
  46. +3 −0 posts/2015-11-11-sharing-secrets-team.md
  47. +3 −0 posts/2015-11-24-architecting-for-continuous-delivery.md
  48. +3 −0 posts/2015-12-02-difference-between-continuous-delivery-continuous-deployment-infographic.md
  49. +3 −0 posts/2015-12-15-tramchester-ian-cartwright.md
  50. +3 −0 posts/2016-01-05-ebook-continuous-deployment-strategies-implementation-techniques.md
  51. +3 −0 posts/2016-01-12-snap-shell-debugger-feature.md
  52. +3 −0 posts/2016-01-20-why-we-dont-use-estimates.md
  53. +3 −0 posts/2016-01-21-snap-ci-digest-january-2016.md
  54. +3 −0 posts/2016-01-25-three-key-deployment-pipeline-patterns.md
  55. +3 −0 posts/2016-02-09-continuous-deployment-static-website-aws-snap-ci.md
  56. +3 −0 posts/2016-03-01-5-half-reasons-product-manager-loves-baremetrics.md
  57. +3 −0 posts/2016-03-22-fail-fast.md
  58. +3 −0 posts/2016-03-25-snap-ci-digest-march-2016.md
  59. +3 −0 posts/2016-03-29-scaling agile-continuous-delivery-b2b-nation.md
  60. +3 −0 posts/2016-04-04-video-do-you-devops.md
  61. +3 −0 posts/2016-04-05-press-release-snap-ci-gocd-showcase-innovation-continuous-delivery-devopsdays.md
  62. +3 −0 posts/2016-04-12-wtf-are-containers.md
  63. +3 −0 posts/2016-04-19-serverless-architecture.md
  64. +3 −0 posts/2016-04-24-serverless-architecture-live-stream-video-play-on-sports.md
  65. +3 −0 posts/2016-04-28-snap-ci-continuous-delivery-integration-tool-launch.md
  66. +3 −0 posts/2016-05-03-serverless-architecture-burst-traffic-applauze.md
  67. +3 −0 posts/2016-05-05-snap-support-troubleshooting-tips.md
  68. +3 −0 posts/2016-05-10-continuous-integration-introverts.md
  69. +3 −0 posts/2016-05-17-snap-support-package-upgrades.md
  70. +3 −0 posts/2016-05-24-wtf-continuous-delivery.md
  71. +3 −0 posts/2016-05-25-devops-roadtrip-seattle.md
  72. +3 −0 posts/2016-05-30-serverless-architecture-aws-lambda-dynamodb-applauze.md
  73. +3 −0 posts/2016-06-07-software-delivery-adventures.md
  74. +3 −0 posts/2016-06-09-aurora-and-cybele-snap-ci-stacks.md
  75. +3 −0 posts/2016-06-14-mercycorps-unhcr-translation-cards.md
  76. +3 −0 posts/2016-06-17-snap-ci-dark-launch-feature-toggles.md
  77. +3 −0 posts/2016-06-21-snap-support-common-npm-issues.md
  78. +3 −0 posts/2016-06-28-continuous-delivery-product-managers.md
  79. +3 −0 posts/2016-07-05-chef-cookbooks-structure-code.md
  80. +3 −0 posts/2016-07-12-project-tintin-charity-continuous-integration.md
  81. +3 −0 posts/2016-07-19-serverless-deployment-lambda-swagger.md
  82. +3 −0 posts/2016-07-26-continuous-delivery-integration-devops-research.md
  83. +3 −0 posts/2016-08-02-failure-option-part-one.md
  84. +3 −0 posts/2016-08-09-failure-option-feature-toggles-part-two.md
  85. +3 −0 posts/2016-08-16-failure-option-lessons-snap-ci.md
  86. +3 −0 posts/2016-08-23-blue-green-deployments-with-chef.md
  87. +3 −0 posts/2016-08-30-5-ways-build-test-deploy-software-fast.md
  88. +3 −0 posts/2016-09-06-continuous-delivery-devops-product-managers-best-friend.md
  89. +3 −0 posts/2016-09-13-snap-ci-different-better-than-jenkins.md
  90. +3 −0 posts/2016-09-27-zero-one-infinity.md
  91. +3 −0 posts/2016-10-04-five-lessons-github-universe.md
  92. +3 −0 posts/2016-10-10-why-thoughtworks-tech-radar-snap-ci-jenkins-mess.md
  93. +3 −0 posts/2016-10-19-rubyconf.md
  94. +3 −0 posts/2016-10-25-how-linux-containers-work.md
  95. +3 −0 posts/2016-11-01-using-lxd-cgroups.md
  96. +3 −0 posts/2016-11-15-wtf-deployment-build-pipelines.md
  97. +3 −0 posts/2016-11-22-deploy-digital-ocean-scp-ssh.md
  98. +3 −0 posts/2016-12-06-deploy-faster-snap-ci-s3-caching.md
  99. +3 −0 posts/2016-12-13-top articles-continuous-integration-delivery-serverless-architecture-2016.md
  100. +3 −0 posts/2017-01-17-lessons-from-product-manager-snap-ci.md
  101. +3 −0 posts/2017-02-06-2017-02-06-snap-announcement.md
@@ -13,3 +13,6 @@ You probably woke up this morning with a new idea for a web app. You want to bui
Your team writes tests and run them locally - but you really can't be bothered to set up a CI server. Not even the 10 minutes it takes you to download one. Not the hour or so it will take you to get all the required libraries and dependencies installed. Not the 20 minutes it would take you to set up a build after all this. And you certainly do not want to baby sit the machine, managing upgrades and downtimes. That is the couple of hours a week that you just do not have - or even if you do, you would much rather spend learning a new language or framework - or maybe even get some sleep?!
If your web application development framework follows conventions and if deploying your application to production is a single Git command you run from your terminal, isn't it time your CI tool learnt about those conventions and decided to do the provisioning of the machine, configuring libraries and setting up your CI pipeline- all out of the box without you having to tell it the same things over and over again? Isn't it 2012 already?
Snap CI © 2017, ThoughtWorks
@@ -14,3 +14,6 @@ Last time around, I claimed that taking time to set up infrastructure for builds
At the surface it might look like these two statements are mutually incompatible. However, what if all that it took to get your Rails application on Github, through a build/deploy pipeline, through into an application deployed on Heroku was a couple of clicks? What if someone took the pain of setting up the machines and configuring your CI server away from you? What if, as you added Javascript tests and some Capybara tests, someone automatically detected that you had done that, and set up all that was needed to run those for you?
{% youtube _q4sk4pJKHA 480 320 %}
Snap CI © 2017, ThoughtWorks
@@ -20,3 +20,6 @@ So in addition to having the ability to configure multiple deployments, you woul
When combined these two features form a core part of creating a build pipeline in Snap.
{% youtube XofmSr2WyAo 480 320 %}
Snap CI © 2017, ThoughtWorks
@@ -17,3 +17,6 @@ However, all these changes happen on a new branch. The code changes, along with
To help with this, Snap now has the ability to clone an existing build pipeline, but point it at a different source tree/branch. Within minutes, your new patch can be tested, integrated and pushed out to production.
{% youtube ZmubQW03K1U 480 320 %}
Snap CI © 2017, ThoughtWorks
@@ -22,3 +22,6 @@ The key benefits of automating deployments and having them modelled as stages in
The following image shows the recent deployment history for the Snap [documentation site](http://docs.snap-ci.com). The first stage generates the website using Jekyll and the subsequent stages which deploy to staging and production sync it to an S3 bucket. And yes, this does mean that deployments in Snap are not limited to just Heroku! That's a different blog post for another day, though. :)
<img src="/assets/images/screenshots/deployment-history@2x.png" class="screenshot"/>
Snap CI © 2017, ThoughtWorks
@@ -13,3 +13,6 @@ We're excited to announce that we're adding support for 3 of the most requested
To that end we are making CouchDB, MongoDB and Redis generally available for all builds. You may access these databases over on their default ports. We have disabled authentication, so your builds should be able to connect to them unauthenticated. As part of our "builds should start from a clean slate" philosophy these databases will be cleaned out before every build.
You can read more about this in [our documentation]({{ site.link.docs }}databases/). And as always, [contact us]({{ site.link.contact_us }}) if there's a feature you'd like to see on Snap.
Snap CI © 2017, ThoughtWorks
@@ -11,3 +11,6 @@ categories: heroku oauth deployments
Snap now uses the new Platform API for Heroku. Specifically, we use [OAuth for Heroku](https://blog.heroku.com/archives/2013/7/22/oauth-for-platform-api-in-public-beta) for [setting up deployments]({{site.link.docs}}deployments/heroku_deployments). Using Heroku OAuth makes Snap a single point of contact for deploying your code to an existing app on Heroku or even creating a new app for deployments.
Using OAuth means that you no longer need to copy over the API key from Heroku. Authorize Snap on Heroku once and Snap takes care of the rest of the deployments.
Snap CI © 2017, ThoughtWorks
@@ -75,3 +75,6 @@ Your Heroku deployment stage should look something like this
<img src="/assets/images/screenshots/dropwizard/heroku-stage.png" class="screenshot"/>
That's all there is to it. Snap will now monitor your repository and run builds for all commits. Snap has a lot more to offer from CCTray, HipChat and Campfire build notifications to manual gated deployments to production environments. Also, we're just getting warmed up. If there's a feature you'd like to see or if you just want to say hi feel free to [contact us]({{ site.link.contact_us }}).
Snap CI © 2017, ThoughtWorks
@@ -73,3 +73,6 @@ Enter "Build" in "STAGE NAME" and "./sbt clean test" in "Tasks to be executed".
Click "Create Project"
That’s all there is to it. Snap will now monitor your repository and run builds for all commits. Snap has a lot more to offer from CCTray, HipChat and Campfire build notifications to manual gated deployments to production environments. Also, we’re just getting warmed up. If there’s a feature you’d like to see or if you just want to say hi feel free to [contact us]({{ site.link.contact_us }}).
Snap CI © 2017, ThoughtWorks
@@ -89,3 +89,6 @@ Now that you have the Deploy stage added to your pipeline, click the Save and Re
![elastic beanstalk dashboard]({% asset_path screenshots/aws-elastic-beanstalk/elastic-beanstalk-dashboard.png %}){: .screenshot}
For more information see [AWS CLI reference](http://docs.aws.amazon.com/cli/latest/reference/), [Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/Welcome.html).
Snap CI © 2017, ThoughtWorks
@@ -52,3 +52,6 @@ We hope that you find this useful.
Note: We are aware that the integration pipeline feature does not address two other possible issues. If multiple members each have a feature branch, there may be some interest in nominating multiple integration targets instead of just one.
In addition, there is definitely a case to be made for triggering the integration pipeline not just for feature branch changes - but also any time the integration target changes. We have some ideas around resolving both of these issues, but in the spirit of releasing early and often, we thought we'ed throw this out there first and see what you have to say about it before moving on to solving those problems.
Snap CI © 2017, ThoughtWorks
@@ -117,3 +117,6 @@ test:
"S3": "S3::FakeS3"
"Github": "Github::FakeGithub"
```
Snap CI © 2017, ThoughtWorks
@@ -33,3 +33,6 @@ We believe we have taken all necessary precautions to get Snap secure for now. I
Stay safe!
Snap CI © 2017, ThoughtWorks
@@ -17,3 +17,6 @@ When setting up a build for your Ruby gem on Snap (we detect the presence of a `
This functionality can be combined with [Automatic Branch Tracking](/blog/2013/11/07/automatic-branch-tracking-and-integration/) to release from a named branch instead too, though in this case, you would need to configure the `Release` stage manually.
Following on the heels of [yesterday's announcement](https://bit.ly/1qAIUVJ), since most Ruby gems are Open Source or at least public, you can start using this today for free!
Snap CI © 2017, ThoughtWorks
@@ -111,3 +111,6 @@ This history allow you to check all previous changes that got deployed and which
With these examples I hope I have explained what differentiates Snap from similar offerings. The name and basic features appear less similar as soon as you start to dig deeper and compare other features. The practice of Continuous Integration is a subset of Continuous Delivery. However, a tool for doing CI cannot be trivially extended to support Continuous Delivery - even if it allows you to configure a deployment at the end of your build.
This explicit focus on features that enable Continuous Delivery is the primary difference about Snap.
Snap CI © 2017, ThoughtWorks
@@ -30,3 +30,6 @@ Here's a quick video to demonstrate this feature:
{% youtube 2E4civiDmtc 480 320 %}
Read some of our other posts on [Snap Shell](https://blog.snap-ci.com/categories/snap-shell/).
Snap CI © 2017, ThoughtWorks
@@ -25,3 +25,6 @@ Lastly, I may not be in a position to merge pull-requests as soon as they come i
To help with this, we not only say _when_ Snap declared the pull-request healthy; we also let you re-run the build when you are ready to merge the pull-request - just to make sure that things are still kosher. Read more about this in [our documentation](http://docs.snap-ci.com/working-with-branches/pull-requests/).
What other collaboration workflows do you have that you think could be made more productive by Snap? Let me know in the comments below!
Snap CI © 2017, ThoughtWorks
@@ -48,3 +48,6 @@ In a minute or two, the build completes and you can see the test results.
Of course, this is just the start. You can use Snap to extend your build in a lot of different directions from here. You can pack and release the jars. If you were building an application, you can configure deployments following the initial stage. See the [What's next section](http://docs.snap-ci.com/getting-started/#whats-next) of our documentation for details on some of these!
Note: The first build usually runs slightly longer as it needs to download all dependent jars from either maven-central or clojars. These jars are automatically cached and subsequent runs will run much faster!
Snap CI © 2017, ThoughtWorks
@@ -21,3 +21,6 @@ We have no reason to believe that any unauthorized access was made or that any d
We believe we have taken all necessary precautions to get Snap secure for now. If you have any further questions or concerns, please do not hesitate to [get in touch with us](https://snap-ci.com/contact-us). We would love to help out in any way we can.
Stay safe!
Snap CI © 2017, ThoughtWorks
@@ -55,3 +55,6 @@ You can find the AWS credentials [here](https://console.aws.amazon.com/iam/home?
That's it, it takes 3 simple steps to setup a deployment to your OpsWorks stack from Snap. Isn't it simple? Hope you enjoy deploying from Snap! I would love to hear if you have any comments or tips to make this experience even better. Leave your comments below or [contact us]({{ site.link.contact_us }}) if you have any questions.
Snap CI © 2017, ThoughtWorks
@@ -54,3 +54,6 @@ Have a look at our [docs](http://docs.snap-ci.com/deployments/aws-deployments/#u
![AWS console for Application name]({% asset_path screenshots/aws-elastic-beanstalk-revisited/elastic-beanstalk-dashboard-deployed@2x.png %}){: .screenshot .big}
As always, I would love to hear if you have any comments or tips to make this experience even better. Leave your comments below or [contact us]({{ site.link.contact_us }}) if you have any questions.
Snap CI © 2017, ThoughtWorks
@@ -69,3 +69,6 @@ $ bundle exec rake spec:smokes
```
These are just a few examples for you to get an idea of the impact the changes may have on your build. You can make these changes right away and your build should continue to work just fine. In case you don't get a chance to update your configuration, we will run a migration that make sure your builds continue to work exactly as they do today. This change will go in effect on Wednesday, Nov 5th, 2014 around evening UTC. If you have any doubts or problems with the changes coming in please feel free to comment below or get in [touch with us]({{ site.link.contact_us }}).
Snap CI © 2017, ThoughtWorks
@@ -44,3 +44,6 @@ git push ssh://ABCDEFGHIJK123@example.yourdomain.rhcloud.com/~/git/example.git/
```
Re-run the build, check your logs, and it should deploy. Good luck!
Snap CI © 2017, ThoughtWorks
@@ -19,3 +19,6 @@ In order to assist with making your tests go faster, we have provided a [ruby ge
If you are not running a ruby project, don't worry, we provide a quick howto on how you can go about quickly [splitting your test suite]({{ site.link.docs }}speeding-up-builds/test-parallelism/).
As always, we would love to hear if you have any comments or tips to make your builds even better. Leave your comments below or [contact us]({{ site.link.contact_us }}) if you have any questions.
Snap CI © 2017, ThoughtWorks
@@ -19,3 +19,6 @@ You can read more about this feature in our [documentation]({{ site.link.docs }}
![bigger workers]({% asset_path screenshots/bigger-workers/bigger-worker-configuation.png %}){: .screenshot .big}
As always, we would love to hear if you have any comments or tips to make your builds even better. Leave your comments below or [contact us]({{ site.link.contact_us }}) if you have any questions.
Snap CI © 2017, ThoughtWorks
@@ -34,3 +34,6 @@ Over the last few weeks, we have spent time consolidating all these mechanisms o
![notification center]({% asset_path screenshots/notifications/notification-center.png %}){: .screenshot .big}
We would love to hear what you think of the new consolidated notification center. Do you see all the channels you expected to see? See anything missing? Let us know in the comments below.
Snap CI © 2017, ThoughtWorks
@@ -35,3 +35,6 @@ I want Snap to be a well-known, reliable service for people who don't have time
#### What's your favorite part of your workday?
I really enjoy getting feedback from clients. It's nice when the client is very happy, and then two weeks later they're buying it. It's very rewarding.
Snap CI © 2017, ThoughtWorks
@@ -29,3 +29,6 @@ Submit your posts here: [https://www.airpair.com/100k­writing­competition](htt
And don't forget to tell us about your posts so we can share them with our audiences too. This is a great opportunity to stretch your skillset AND gain a following while winning cash. Win-win-win.
Never done social authoring before? Got [questions](https://www.airpair.com/100k-writing-competition/faq)? AirPair has an [easy how-to](https://www.airpair.com/social-authoring) to help you begin. Looking forward to reading all your awesome contributions!
Snap CI © 2017, ThoughtWorks
@@ -29,3 +29,6 @@ We've removed bower and grunt as part of the node installations since most users
As and when new versions are released and available, they will automatically be available to Snap users. If a binary is not available, then you may get in touch with us, and we'll make it available ASAP.
If you have any comments or tips to help us improve, let us know by dropping a comment below or [contact us]({{ site.link.contact_us }}) if you have any questions.
Snap CI © 2017, ThoughtWorks
@@ -45,3 +45,6 @@ This particular approach is not recommended for changing public DNS records beca
This approach is a combination of the two techniques we've seen so far.
In this technique, instead of changing public DNS records, we'll change internal (private) DNS records. Since the internal network and the DNS server can be managed and configured to respect TTLs, this approach works a lot better than changing public DNS records.
Snap CI © 2017, ThoughtWorks
@@ -31,3 +31,6 @@ As your confidence in the deployment improves, you can deploy your application t
## Long running migration phase
Because one or more versions of your application may be running in production for some period of time, your application and its components (webservices, microservices, database) needs to be backward-compatible so that it works with at least one or two previous versions of your application. This [Parallel-Change Pattern](http://martinfowler.com/bliki/ParallelChange.html) is a simple and effective way to implement backward-incompatible changes between application interfaces.
Snap CI © 2017, ThoughtWorks
@@ -22,3 +22,6 @@ Snap's product owner [Badri Janakiraman](https://github.com/badrij) and develope
* Kick the can down the road.
You can watch the video below and download the slides from the talk [here](https://pipelineconf.files.wordpress.com/2014/03/badri-akshay-cd-is-a-journey2015.pdf).
Snap CI © 2017, ThoughtWorks
@@ -68,3 +68,6 @@ This technique can also be used to do some interesting multi-variant testing and
## Next steps
In my next post, I'll get into the implementation techniques of blue/green deployments. A subsequent post will talk about implementing canary releases. Hope you will find this series very useful.
Snap CI © 2017, ThoughtWorks
@@ -94,3 +94,6 @@ The Stage History view can help you determine just that and help you to immediat
![stage history]({% asset_path screenshots/multi-stage-builds/stage_history.png %}){: .screenshot .big}
I hope you now that you've read this you have a better picture of how to leverage stages in your Snap CI pipelines. Feel free to reach out to us in case of questions or feedback.
Snap CI © 2017, ThoughtWorks
@@ -21,3 +21,6 @@ Not anymore.
We are glad to announce that you can now pin such variables just like any command. This has long been requested and we hope that it makes managing build configuration easier for users.
More details can be found on our [docs](https://docs.snap-ci.com/pipeline/#environment-variables%23global-environment-variables).
Snap CI © 2017, ThoughtWorks
@@ -80,3 +80,6 @@ If you're interested in using Docker on Snap CI, [you can sign up here](https://
[IBMResearchReport]: http://domino.research.ibm.com/library/cyberdig.nsf/papers/0929052195DD819C85257D2300681E7B/$File/rc25482.pdf "Performance comparison of Virtual Machines and Linux Containers"
[UserNamespaces]: https://lwn.net/Articles/532593/ "User namespaces in Linux"
Snap CI © 2017, ThoughtWorks
@@ -92,3 +92,6 @@ So in general when you want to package and distribute your application as compon
In the next article, we will look at the security aspects of running containers. Stay tuned!
A version of this article originally appeared on [RisingStack](https://blog.risingstack.com/operating-system-containers-vs-application-containers/)
Snap CI © 2017, ThoughtWorks
@@ -77,3 +77,6 @@ The team will continue to investigate the upgrade to the newest versions of Ruby
Our experience using Canary Releases proved to be successful and clients can now consider this as an option when they have a risky releases planned.
This post was originally published on [ThoughtWorks Insights](http://www.thoughtworks.com/insights/blog/how-deliver-rails-upgrade-using-canary-release) Continuous Delivery channel.
Snap CI © 2017, ThoughtWorks
@@ -39,3 +39,6 @@ On the other hand, LXC now has [support for user namespaces](https://www.stgrabe
Due to these considerations, we selected [unprivileged LXC containers](https://linuxcontainers.org/lxc/getting-started/#creating-unprivileged-containers-as-a-user) for build machines on top of which users will be able to build and run Docker containers.
*If you’re interested in using Docker on Snap CI, [sign up here](https://orca.snap-ci.com/).*
Snap CI © 2017, ThoughtWorks
@@ -76,3 +76,6 @@ Once the build completes, GitHub reflects the status of the build on the pull re
I now know that the pull request can be safely merged to the master!
<span style="font-style:italic">This article is Part 1 in a series from our upcoming e-Book "CD with Snap CI"</span>
Snap CI © 2017, ThoughtWorks
@@ -31,3 +31,6 @@ It's a sort of a [Goldberg Machine](https://en.wikipedia.org/wiki/Rube_Goldberg_
For this script to work you need [fswatch](https://github.com/emcrisostomo/fswatch), [jq](http://stedolan.github.io/jq/) and [cURL](http://curl.haxx.se/). Note that I save my API key in my keychain. If you're not using a Mac, you need to figure a way to keep it a secret.
<span style="font-style:italic">This article was originally featured on [Marco Valtas' blog](http://marcovaltas.com/)</span>
Snap CI © 2017, ThoughtWorks
Oops, something went wrong.

0 comments on commit 79aefee

Please sign in to comment.