Tag Archives: continuous integration

Travis CI Tutorial: Getting Started

via Travis CI Tutorial: Getting Started – Ray Wenderlich.

Thankfully, Continuous Integration can save the day. Continuous Integration, often abbreviated to just CI, is the process of automatically building and running tests whenever a change is committed.

Now, Apple has their own solution for this with Xcode Bots, which are designed to run on OS X Server. But the downside of Apple’s solution is that you, yes you have to manage the entire process. You have to set up and maintain OS X Server and Xcode versions on the server, figure out access control for viewing results, and handle provisioning and signing issues. Sounds like a lot of work, right? You don’t have time for this; you have code to write, apps to design, and happy hour to get to – that beer isn’t going to drink itself.

Shout it to the cosmos with me: there must be an easier way!

Fasten your seat belts: Flying the Oracle Development Cloud Service (1- Boarding)

I’ll begin new a series about my findings on working with the Oracle Development Cloud Service. I’m not sure how many post will finally be part of this series, but I guess you’ll see a couple. Before we begin lets ask the big question: What is the Oracle Oracle Development Cloud Service and what do […]


Using an Artefact Repository

Many development teams still use a network drive to store artefacts. This method of transferring artefacts can be unstructured and differ between teams. Thus, it is better to use the advantages of an Artefact Repository.



This is a multi-part documentation of how to setup a CI/CD workflow in AWS. Some of the tools that will be used are EC2, Chef, CloudFormation, Jenkins, Rspec, and Apache. If you have questions feel free to leave a comment or track me down on Twitter at @devopshomelab Part 1 – Workstation Setup – The […]


Jenkins to Nexus with Git Polling

via Jenkins to Nexus with Git Polling – Tech Tip #76 – Miles to go 2.0 ….

Build Binaries Only Once is a very important principle of Continuous Deployment (CD). However that blog guides you to build and deploy binaries to Nexus from your development machine. This is fine as a starting step where everything is locally contained on your laptop and you are just testing setup to figure out how things work. But everybody in the team having a local Nexus repository defies the purpose of a “shared repository”.  This is also against Continuous Integration (CI) where the source code committed by different team members checked out and build on a CI server. And CI is a fundamental requirement for Continuous Deployment. How do you set this up then?

You use a CI server to push binaries to Nexus.

There are a varety of CI servers in both open source and commercial range. Jenkins, Travis,  CruiseControl and Go are some of the popular ones in the open source land. They all have a commercial edition as well. Bamboo and AnthillPro are a couple of popular commercial-only offerings. This blog will use the simplest, most popular, and easiest to use Jenkins CI server.

Node With Docker – Continuous Integration and Delivery

via Node with Docker – continuous integration and delivery – Michael Herman.

This is a quick start guide for spinning up Docker containers that run NodeJS and Redis. We’ll look at a basic development workflow to manage the local development of an app, on Mac OS X, as well as continuous integration and delivery, step by step.

We’ll be using the following tools, technologies, and services in this post:

  1. NodeJS v0.12.0
  2. Express v3.4.8
  3. Redis v2.8.19
  4. Docker v1.5.0
  5. boot2docker v1.5.0
  6. Docker Compose v1.1.0
  7. Docker Hub
  8. CircleCI
  9. Digital Ocean
  10. Tutum

Video: NodeJS Continuous Integration to Delivery

In this talk, Adron Hall (visiting from Portland!) shows how to go from a minimal Node project, to fully deployed web site including a fully integrated and operative continuous integration and delivery pipeline. He’ll also dive into some basic practices around test or behavior driven development within JavaScript to build a full server to client website and have that website deployed, tested – on both client and server, and deployed auto-magically to a live site.