Talk:Continuous deployment

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Software: Computing Low‑importance

	This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.SoftwareWikipedia:WikiProject SoftwareTemplate:WikiProject Softwaresoftware
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Computing.

Engineering Low‑importance

	Engineering portal This article is within the scope of WikiProject Engineering, a collaborative effort to improve the coverage of engineering on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.EngineeringWikipedia:WikiProject EngineeringTemplate:WikiProject EngineeringEngineering
Low	This article has been rated as Low-importance on the project's importance scale.

Continuous deployment as technology not process

I'd argue that Continuous Deployment is the automation technology wherein your Continuous Integration servers can push out new releases of the code into staging, perhaps production. In contrast, Continuous Delivery is how to use this, code patterns (feature flags) and software development practices in order to be able to rapidly and iteratively develop and ship software.

SteveLoughran (talk) 16:30, 20 February 2024 (UTC)[reply]