This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Continuous Delivery
Continuous Delivery

Version management

Difference between version and

At line 1 added 396 lines
!!! Overview
[{$pagename}] ([CD] or [Continuous Development]) is a [Software development practice] where code changes are automatically built, tested, and prepared for [Production tier] [release].
[{$pagename}] is part of the [CI]/[CD] Pipeline.
[{$pagename}] is closely related to [Continuous integration] and refers preparation of [software] that passes the automated [Testing]. ([Definition of Done])
"Essentially, it is the practice of releasing every good build to users”, explains Jez Humble, author of [{$pagename}].
By adopting both [Continuous integration] and [{$pagename}], you not only reduce risks and catch [bugs] quickly, but also move rapidly to working software.
With low-risk releases, it is easier and faster to provide [Business value]. This fosters for greater collaboration between [dev] and [Ops], fueling real change in your organization, and turning your release process into a business advantage.
Allow a [Responsive Organizations] to perform [{$pagename}] often using [DevOps]
!! [{$pagename}] is not [Production tier] [Release]
One misconception about continuous delivery is that it means every change committed is applied to production immediately after passing automated tests. However, the point of [{$pagename}] is not to apply every change to [Production tier] immediately, but to ensure that every change is ready to go to [Production tier].
%%warning
[{$pagename}] is a __[Development Team]'s [Definition of Done]__. The decision to move to the [Production tier] is a business decision usually by the [Product Owner]
%%
[{$pagename}] may be a [Development Team] decision in some environments when release is a [Bounded Context] of a [Software library] not changing the [API] or interface as in [Microservice] [Architecture]
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Architecting for Continuous Delivery|https://www.thoughtworks.com/insights/blog/architecting-continuous-delivery|target='_blank'] - based on information obtained 2017-07-03
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop