Go.cd is a tool for continuous delivery that allows software to be delivered incrementally with reduced cost, time, and risk. It features continuous integration by providing feedback at the build, deployment, and feature stages. Go.cd's core includes a Go Server, REST API, and Go Agents that run on tags in controlled environments. Pipelines define the workflow with stages for logical steps and jobs that run tasks in parallel. Pipelines have run histories that allow re-running and manual triggering at the pipeline, stage, and job levels.

1. Go.cd -
the tool that is
what Jenkins ain't

2. Go.cd är ett verktyg för
Continuous Delivery

3. Continuous Delivery is
an approach to delivering software that
reduces the cost, time and risk
of delivering incremental changes to users.

4. C. Integration: ability to integrate easily
C. Delivery: release on demand
C. Deployment: release is default

5. C. Integration: feedback @ build
C. Delivery: feedback @ deploy
C. Deployment: feedback @ feature

6. Open Sourced 4 mars 2014, APL

7. Core Features
Go Server
center of universe, pipelines UI, ...
RESTful HTTP API for most everything
Go Agents - workers
tags (java8, android, gradle, ...)
environments: build, FT, NFT, stage, prod, ...

8. Agents

9. Environments

10. Pipeline: Top level building block

11. Pipeline » Stage: Logical steps, in sequence

12. Pipeline » Stage » Job: Run in parallel!

13. Pipeline » Stage » Job » Task: Run in sequence

18. Pipeline: Run history, re-run, manual triggers

19. Pipeline » Stage: Run history, re-run

20. Pipeline » Stage » Job: Console log

21. Pipeline » Stage » Job: Inspect artifacts

22. Pipeline » Stage » Job: Artifacts!

23. Core Features - config, data and logs
➔ One XML config file - version controlled
➔ Data & statistics in SQL database

25. Enterprise Features
Connects to AD
Restrict access to pipeline groups,
environments, actions, role, ...
Retrigger jobs
Auditable
Commercial support

26. Features - pipeline templates

27. Summary - diff to Jenkins
Version control EVERYTHING
Visualizing work flow is not a plugin
Modeling how work flows is predictable
Enterprise ready out of the box
Proper fan-in control
Properties for metrics collection

28. Future
Enable elastic scaling of agents
Smart test runner
- run failed tests first
- massive parellelization
Improve pipelines view performance
Large scale improvements
Improved notifications abilities

29. How long would it take your organization to
deploy a change that involved
just one single line of code?
Do you do this on
a repeatable, reliable basis?