Skip to content

Commit

Permalink
Week 3: Demo proposal (lvainio + oscols) (#2418)
Browse files Browse the repository at this point in the history
* Added week2 readme

* Update Presentation Proposal

* Update README.md

* Update README.md

* Final update to README.md

* add demo week3

---------

Co-authored-by: oscols <[email protected]>
  • Loading branch information
lvainio and oscols authored Sep 7, 2024
1 parent 2f8c43e commit c5f565a
Showing 1 changed file with 30 additions and 0 deletions.
30 changes: 30 additions & 0 deletions contributions/demo/week3/lvainio-oscols/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Assignment Proposal

## Title

From Continuous Delivery to Continuous Deployment in GoCD with Gomatic.


## Names and KTH ID

- Leo Vainio ([email protected])
- Oscar Olsson ([email protected])

## Deadline

- Week 3

## Category

- Demo

## Description

Story: Manager wants to go from Continuous Delivery to Continuous Deployment using the same platform (GoCD).

We will demonstrate how we can change the configuration in GoCD to go from Continuous Delivery to Continuous Deployment. We will use a small example project for this demo and we will use Gomatic to allow us to configure the GoCD pipeline in code.


**Relevance**

GoCD is a CI/CD tool which is useful to know how to use. Also, it’s important to understand the difference between Continuous Delivery and Continuous Deployment and in this demo our goal is to illustrate the main differences. In Continuous Delivery, changes that pass automated tests still need manual approval but in Continuous Deployment even the deployment step is automated.

0 comments on commit c5f565a

Please sign in to comment.