Continuous Delivery with ThoughtWorks Go

Note: These posts were written a while ago and might be out of date.

Introduction

This is meant to be an unofficial, unsupported blog about ThoughtWorks' agile release engineering, continuous delivery orchestrator tool called Go. The opinions expressed here are personal and not necessarily those of my employer.
Posted by sriram on Monday, June 25, 2012
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Newer Post Home

Search This Blog

Testimonials

What Go users say

Index

  • The power of pipeline templates and parameters
  • Modeling higher order workflows with Go
  • Go environments
  • Traceability with upstream pipeline labeling
  • Go illustrated
  • Does Go support my favorite build/deployment tool?
  • Why continuous delivery needs devops, and why devops needs infrastructure-as-code
  • Users write/talk about Go
  • Pipelines and Value Streams
  • Choose wisely between Pipelines, Stages, Jobs and Tasks
  • Werner Vogels shows off Go
  • Mapping TeamCity to Go
  • Monitor Go Agents with Graphite
  • One task per job
  • Go + Maven + Chef
  • A command repository for Go
  • How to peg your pipeline to a dependency version
  • Drive Go from Jenkins
  • Pass variables to other pipelines
  • Timer pipelines that don't overwhelm the repository

External Resources

  • Go info console utility
  • Time since last green build
  • Chef cookbooks for Go server and agent
  • Alternative dashboard for Go
  • Go API client ruby gem
  • One-click admin, log coloring

Also see

Webinars from #twstudios

Home Page

Pricing

Insights into CD

CD@TW

TW-CD on YouTube

TW-Studios on YouTube

MF on CD

Jez's site

About me

www.agileorgdesign.com
Simple theme. Powered by Blogger.