Deploying code to Amazon OpsWorks using Codeship
Here, at Novo IT, we love using Amazon OpsWorks for deploying our internal
projects. With OpsWorks, we can easily segregate our development environments
in Stacks and control how each project gets built via Chef recipes. OpsWorks
binds directly with your code repository of choice. When you initiate a new
build, it will pull in the latest changes and build them for you.
One task, that is not immediately obvious how to solve, is triggering an
OpsWorks build remotely from the command line, or from a build server. This
article will explain how we do exactly this, using the excellent Codeship
Continuous Integration and Deployment service.
Setting up a new IAM user on AWS
We will make use of the AWS Identity and Access Management (IAM) feature to
create a new user for our deployments. This is preferable to using, say your
If you have a slow test suite and you are asking yourself "how can I make my
tests faster?" then you are asking the wrong question. Most chances are that
you have bigger problems than just slow tests. The test slowness is merely
the symptom; what you should really address is the cause. Once the real cause
is addressed you will find that it's easy to write new fast tests and
straightforward to refactor existing tests.
It's surprising how quickly a rails app's test suite can become slow. It's
important to understand the reason for this slowness early on and address the
real cause ... (more)
This is a republished blog post. You can find the original source here:
Using Pull Requests
As I mentioned last week we use GitHub Flow on GitHub. But the whole
workflow we describe is also possible when working with BitBucket. We do not
have a policy when a pull request should be opened. Some of our developers
open them when they start a feature, some wait until the feature is
implemented. Then we push regularly to that branch as explained in the last
Open pull requests are h... (more)
This is the 20th Testing Tuesday episode. Every week we will share our
insights and opinions on the software testing space. Drop by every Tuesday to
learn more! Last week we started testing node.js applications with Jasmine.
How to deploy a node.js app to Heroku
In this screencast we’ll deploy a very simple node.js web application to
Heroku continuously with the help of the Codeship.
Disclaimer: We show a lot of the Codeship in this screencast – that’s
because we use it and because we build it. There are certainly other ways to
continuously deploy node.js applications. This is how... (more)
Last week we talked about how we review code, open pull requests and use
GitHub issues to manage our development workflow.
This week I will show you every step that happens after a pull request is
merged into our master branch. We use an automated deployment pipeline for
releasing our code into production.
A deployment pipeline lays out the whole process that your code needs to go
through from your repository to production. It breaks the build into several
parts (e.g., build, test and deploy) and all the associated steps that need
to be taken. By defining a p... (more)