Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

An Introduction to Go

382 views

Published on

Agile teams deliver working software early and often. Go automates and streamlines the build-test-release cycle for worry- free, continuous delivery of your product.

http://www.go.cd/

Published in: Education
  • Be the first to comment

An Introduction to Go

  1. 1. GO An Introduction to Go
  2. 2. DIMENSIONS OF A CD TOOL Modeling ■ Components, teams, environments ■ Sequential, parallel, group into pipeline/stage/job ■ Access, authorization, manual-gates ■ Templates Support Failing Fast ■ Fast feedback with shortened cycle-times ■ Break the sequential nature of delivery cycles ■ High parallelization ■ Support the resulting more complex builds 2
  3. 3. Visualization Traceability ■ How far has this commit progressed? ■ What build is deployed to the testing environment? ■ What are the code changes associated with this deployment? ■ What are the commits between any two runs of a pipeline? Auditability ■ Who canceled, paused, manual-triggered this stage/pipeline? ■ How has the pipeline config changed from the last run? 3
  4. 4. Orchestration ■ Poll, schedule, manual, API ■ Unicast, multi-cast ■ Fan-in resolution ■ Timeout, Error handling Automation ■ Loosely coupled ■ Version controlled ■ Endpoint Agnostic 4
  5. 5. GO CONCEPTS 5
  6. 6. USE GO TO 6 1. Build Binaries 2. Build Products
  7. 7. END TO END VIEW 7 VisualizationFail Fast
  8. 8. COMPARE PIPELINE INSTANCES 8 Visualization
  9. 9. 9 Modeling Orchestration
  10. 10. FAN-IN RESOLUTION 10 C A B D C12 A50-C12 B34-C12 D23-A50- B34 c13 A51-C13 B35-C13 No-trigger C14 A52-C14 B36-C14 No-trigger C15 A53-C15 B37-C15 D24-A53- B35 Git A Git B Git C Pipeline A Pipeline B Pipeline C Pipeline D Fan-out Fan-in
  11. 11. 11 Build Orchestration & Automation
  12. 12. 12 Deployment Orchestration & Automation
  13. 13. THANK YOU

×