Enable javascript in your browser for better experience. Need to know to enable it? Go here.
Blogs Banner

Announcing Go 2.1 Early Access, and Cruise EOL

Even though Go 2.0 was only released one month ago, we've already been hard at work adding features for our forthcoming Go 2.1 release. Since Go is supposed to enable rapid, reliable releases, we thought we should demonstrate that we are practicing what we preach. The team is ensuring that Go remains production-ready throughout our development lifecycle, and to prove it - and give you the ability to try out the latest features - we're planning on releasing early access builds every few weeks throughout the development lifecycle.

The 2.1 release is planned for Q4 2010, and we are currently hoping to include the following features, along with a number of smaller improvements:

  • The ability to authorize people to administer the configuration of pipeline groups. This is especially useful if multiple projects/teams share a single Go server - it means boxes can be centrally managed, but teams are in control of their build configuration (DONE)
  • Go automatically detects agent collisions (for example when you clone a VM) and prevents thrashing (DONE)
  • Pipeline level Atom feeds
  • A GUI for creating and configuring environments and for server and user management (a GUI for configuring pipelines will follow in 2.2)
  • Including test failure information in email notifications
  • Enhancements to distributed test failure history reports (commit and stack trace information)
  • Go Pipeline Gadget with Outh 2.0 so that you can embed a view of a pipeline in any compliant OpenSocial container
  • Ensuring that when check-ins affect multiple pipelines, changes propagate through the pipeline dependency graph correctly
  • An option to force agents to perform a clean build, and to bypass version control operations
  • The ability to parameterize templates
  • Authorization to trigger, cancel and re-run automatically triggered stages (DONE)

We look forward to getting your feedback on Go 2.1.

Disclaimer: The statements and opinions expressed in this article are those of the author(s) and do not necessarily reflect the positions of Thoughtworks.

Keep up to date with our latest insights