Go continuous delivery
| Original author(s) | Pooja Chopra |
|---|---|
| Initial release | 2007 (as Cruise)[1] |
| Stable release |
16.2.1[2]
/ February 2016 |
| Written in | Java, Ruby |
| Platform | cross platform |
| Type | software development |
| License | Apache License 2.0 |
| Website |
www |
Go is an open source tool which is used in software development to achieve continuous delivery (CD) of software. It supports automating the entire build-test-release process from code check-in to deployment. It helps to keep producing valuable software in short cycles and ensure that the software can be reliably released at any time.
History
Go was originally developed at ThoughtWorks Studios in 2007 and was called Cruise before being renamed Go in 2010 and released as open source in 2014.[1][3]
Concepts[4]
- A Pipeline consists of multiple stages, each of which will be run in order.
- A Stage consists of multiple jobs, each of which can run independently of the others.
- A Job consists of multiple tasks, each of which will be run in order.
- A Task is an action that needs to be performed. Usually, it is a single command.
- A Material is a cause for a pipeline to run. This could be a commit made to a source code repository or a timer trigger.
- Agents run the jobs assigned to them.
References
- 1 2 Avram, Abel (7 Mar 2014). "ThoughtWorks Open Sources Go, a CD Tool". InfoQ. Retrieved 29 March 2016.
- ↑ "Release Notes". Go Continuous Delivery. Retrieved 29 March 2016.
- ↑ Fowler, Martin (25 March 2014). "Open-Sourcing ThoughtWorks Go". martinfowler.com. Retrieved 29 March 2016.
- ↑ "Introduction". Go User Documentation. Retrieved 29 March 2016.
This article is issued from Wikipedia - version of the 5/19/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.