Safe Continuous Deployment with Blue-Green Deployment - #2978
Draft
TheArtemis wants to merge 1 commit into
Draft
Conversation
ericcornelissen
requested changes
Sep 3, 2026
ericcornelissen
left a comment
ericcornelissen
left a comment
Collaborator
There was a problem hiding this comment.
Thank you for the proposal, it looks good but please add a description of what you plan to do in the demo in addition to a description of what blue-green deployments are.
Also, please mark your pull request as ready for review so we can merge it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Safe Continuous Deployment with Blue-Green Deployment
Names and KTH ID
Deadline
Category
Description
This demo aims to show a simple Continuous Deployment pipeline using blue-green deployment. A new version is deployed to an inactive environment, health checked automatically and only then it is switched to receive oncoming traffic. If the checks fails, the new version is rejected and the current version stays live.
Relevance
Continuous Deployment is an important DevOps practice for releasing changes quickly and safely. This demo shows how important it is the process of failure handling and traffic switching to reduce as much as possible the downtime of production systems.