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
DevOps
DevOps

Version management

Difference between version and

At line 1 added 59 lines
!!! Overview
[{$pagename}] is a [software] management culture and practice [Architecture] [Model] that aims at unifying [Development Team] ([Dev]) and software [Operations Team] ([Ops])
[{$pagename}] main characteristic is to strongly advocate automation and [monitoring] at all steps of [Software Development Life Cycle] by using:
* [Continuous Development]
* [Continuous testing]
* [Continuous Delivery]
* [Continuous integration]
* [Infrastructure As Code] ([IAC])
[{$pagename}] aims at establishing a culture and environment where:
* shorter development cycles ([Iterations])
* increased deployment frequency ([Velocity])
* more dependable [releases]
* close alignment with [Business value]
%%information
No one agrees what [{$pagename}] means. This is just how [{$applicationname}] feels about [{$pagename}]
%%
[{$pagename}] is closely related to the [Cloud Native] [Software development practice]
!! [{$pagename}] toolchain
[{$pagename}] is a cultural shift and collaboration between development, operations and testing, there is no single [{$pagename}] tool, rather a set or “[{$pagename}] toolchain” consisting of multiple tools.
Generally, [{$pagename}] tools fit into one or more of these categories, which is reflective of the [Software Development Life Cycle] ([SDLC]):
* [Code] – [Continuous Development] and review, version control tools, code merging
* Build – [Continuous integration] tools, build status
* Test – [Continuous testing] and results determine performance
* Package – Artifact repository, [application] pre-deployment staging ([Containerization])
* [Release] – Change management, release approvals, [Continuous Delivery]
* Configure – Infrastructure configuration and management, Infrastructure as Code tools ([Container Orchestration])
* [Metric Analysis] - [Application] [Monitoring] and [User Experience] [monitoring]
* REPEAT
!! [{$pagename}] and [Responsive Organizations]
[Responsive Organizations] employ [Agile] techniques and use [Continuous Improvement]/[Continuous Development] tools to meld [application] development, testing, refreshes and quality assurance into an integrated [framework]
Most of those [Responsive Organizations] also have simultaneously discovered the power of [Containerization] methods such as [Docker]. A [Docker] container consists of a complete file system that contains everything, including the code, runtime, system tools and system libraries, which an [application] needs to run.
These capabilities not only makes it easier to package [application] code to make it more portable, but it also enables [Information Technology] organizations to adopt a [microservices] approach to [Information Technology] that makes [applications] more robust and flexible.
Advanced [Responsive Organizations] may also use [Functions as a Service]
!! [{$pagename}] and semantic-release
[semantic-release|https://semantic-release.gitbook.io/semantic-release/|target='_blank'] is a [Node.js] based software [Software library] that perhaps best exemplifies the [{$pagename}] concept.
!! Category
%%category [Programming]%%
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [semantic-release|https://semantic-release.gitbook.io/semantic-release/|target='_blank'] - based on information obtained 2019-09-16
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop