Category / How we do

February 28, 2012

A look inside our Jenkins Pipeline – how we make reliable stuff

jenkins-pipeline-start

We use a tool called Jenkins to do Continuous Integration (often referred to as CI). Without getting too nerdy, all that means is that we have a server sitting in the background continually checking our work. Each time someone changes something, the Jenkins CI server “builds” a completely new version of the site and runs some tests over it.

Read More
February 24, 2012

How a project gets tested and deployed with GitFlow

We’ve started moving all of our projects over to GitFlow, which is a way of managing all the complex changes and workflow involved in making, testing and publishing digital projects. How we manage our test and deploy workflow has changed massively over the years. Many moons ago we started off with no tests, manual publishing …

Read More
January 25, 2012

Jira priorities: the story of Team Six and The Iceberg

jira-screenshot

We use Jira to keep track of all of our tasks – without it we’d be overwhelmed with the sheer volume of “stuff” you need to keep track of on a typical project. For each of our projects, the client can email in issues to our team via a project email address. These emails don’t …

Read More
Newer Posts
Older Posts