Difference between revisions of "New Deployment Pipeline"
| (2 intermediate revisions by one other user not shown) | |||
| Line 9: | Line 9: | ||
It is a common mistake to attempt to complete this task as “one giant leap”. Much easier to grow the pipeline incrementally, and to build upon success. | It is a common mistake to attempt to complete this task as “one giant leap”. Much easier to grow the pipeline incrementally, and to build upon success. | ||
Whatever your starting point, begin the pipeline with a “[[Walking Skeleton]]”. The idea is to use a minimal case to get something into place that works, before dealing with the complexities of the more difficult aspects of “[[Releasability]]” or with running vast builds or executing massive suites of automated test cases. | Whatever your starting point, begin the pipeline with a “[[Access Full MSEC via Patreon|Walking Skeleton]]”. The idea is to use a minimal case to get something into place that works, before dealing with the complexities of the more difficult aspects of “[[Access Full MSEC via Patreon|Releasability]]” or with running vast builds or executing massive suites of automated test cases. | ||
Start first with the “low-hanging fruit”. | Start first with the “low-hanging fruit”. | ||
| Line 19: | Line 19: | ||
Your aim in staring out is to get a basic, functioning, deployment pipeline in-place that will work for your teams, with the technologies that they use. | Your aim in staring out is to get a basic, functioning, deployment pipeline in-place that will work for your teams, with the technologies that they use. | ||
As we have already covered, the goal of a deployment pipeline is to act give you feedback on the ‘[[Releasability]]’ of your changes. | As we have already covered, the goal of a deployment pipeline is to act give you feedback on the ‘[[Access Full MSEC via Patreon|Releasability]]’ of your changes. | ||
The pipeline in the Figure above is what we consider to be the minimum necessary steps to determine [[Releasability]]. Begin the creation of your pipelines by first getting this minimum in-place. | The pipeline in the Figure above is what we consider to be the minimum necessary steps to determine [[Access Full MSEC via Patreon|Releasability]]. Begin the creation of your pipelines by first getting this minimum in-place. | ||
The minimum pipeline has: | The minimum pipeline has: | ||
:* [[Version Control]] | :* [[Access Full MSEC via Patreon|Version Control]] | ||
:* A [[Commit Stage]] for fast, developer-entered [[Feedback]] | :* A [[Access Full MSEC via Patreon|Commit Stage]] for fast, developer-entered [[Access Full MSEC via Patreon|Feedback]] | ||
:* An [[Acceptance Stage]], to confirm that changes are configured correctly, work as part of the whole system and fulfil user-needs. | :* An [[Access Full MSEC via Patreon|Acceptance Stage]], to confirm that changes are configured correctly, work as part of the whole system and fulfil user-needs. | ||
:* Automation that supports deployment into [[Production]]. | :* Automation that supports deployment into [[Access Full MSEC via Patreon|Production]]. | ||
To create this basic, functioning [[Deployment Pipeline|pipeline]], we will need a some of you code to work with. | To create this basic, functioning [[Deployment Pipeline|pipeline]], we will need a some of you code to work with. | ||
| Line 34: | Line 34: | ||
---- | ---- | ||
<span style="color:white;background:red;padding:4px"><big>'''[[Main Page|<span style="color:white">Home</span>]] [[ | ''This is a preview version of '''MSEC'''. The full version is available to [https://www.patreon.com/continuousdelivery Patreon supporters] at the Gemini level and above.'' | ||
''[https://www.patreon.com/continuousdelivery Click here for details] on how to join the growing '''MSEC''' community.'' | |||
---- | |||
<span style="color:white;background:red;padding:4px"><big>'''[[Main Page|<span style="color:white">Home</span>]] [[Access Full MSEC via Patreon|<span style="color:white">Next ></span>]]'''</big></span> | |||
Latest revision as of 15:15, 17 January 2023
This is a preview version of MSEC. The full version is available to Patreon supporters at the Gemini level and above.
Click here for details on how to join the growing MSEC community.
The easiest place to start in creating a new Deployment Pipeline is with a new project of some kind. However, even if you are not starting from scratch, it is good to start with small steps. Build your pipeline incrementally to support your development.
It is a common mistake to attempt to complete this task as “one giant leap”. Much easier to grow the pipeline incrementally, and to build upon success.
Whatever your starting point, begin the pipeline with a “Walking Skeleton”. The idea is to use a minimal case to get something into place that works, before dealing with the complexities of the more difficult aspects of “Releasability” or with running vast builds or executing massive suites of automated test cases.
Start first with the “low-hanging fruit”.
Begin with a Basic Functioning Pipeline
Your aim in staring out is to get a basic, functioning, deployment pipeline in-place that will work for your teams, with the technologies that they use.
As we have already covered, the goal of a deployment pipeline is to act give you feedback on the ‘Releasability’ of your changes.
The pipeline in the Figure above is what we consider to be the minimum necessary steps to determine Releasability. Begin the creation of your pipelines by first getting this minimum in-place.
The minimum pipeline has:
- Version Control
- A Commit Stage for fast, developer-entered Feedback
- An Acceptance Stage, to confirm that changes are configured correctly, work as part of the whole system and fulfil user-needs.
- Automation that supports deployment into Production.
To create this basic, functioning pipeline, we will need a some of you code to work with.
This is a preview version of MSEC. The full version is available to Patreon supporters at the Gemini level and above.
Click here for details on how to join the growing MSEC community.