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 helpful as everyone can see what we are working on.
One really important part of feature branches and pull requests are proper
Writing good commit messages
As a distributed version control system, git makes it easy to take large
changes and split them into small commits. Then... (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)
After reading Chad Fowlers excellent blogpost about immutable deployments at
6Wunderkinder, we wanted to share our views on immutability in
Our definition of Immutable Infrastructure:
Automate the setup and deployment for every part and every layer of your
infrastructure. Never change any part of your system once it is deployed. If
you need to change it, deploy a new system.
For example, instead of deploying into an existing EC2 instance, start a new
server, deploy there and point your load balancer to the new server. Then
remove the old server.
Replacing a syste... (more)
At Usersnap we spend a lot of time thinking about optimizing the developer
workflow. With great tech startups helping us with our tests, and Continuous
Integration, we want to add Continuous Feedback to the dev checklist.
Fortunately we don't need to stress the importance of receiving feedback from
clients, co-workers and users before, during and after your development
process. Let's move on to the how.
We have all read Eric Ries' The Lean Startup - or at least we say we did -
and its call for agile product development and validated learnin... (more)
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 expl... (more)