Comments on: Implementing Continuous Delivery through Five Steps

By: The Complete Guide to Angular Security – Christian Lüdemann

The Complete Guide to Angular Security – Christian Lüdemann — Tue, 02 Mar 2021 17:04:09 +0000

[…] teams, in this day and age, are usually autonomous DevOps teams and use continuous delivery for faster feature delivery. This way of working is only possible if we, frontend developers, also […]

By: Angular Projects and Lessons Learned – Christian Lüdemann

Angular Projects and Lessons Learned – Christian Lüdemann — Thu, 16 Jan 2020 06:21:46 +0000

[…] to implement real continuous delivery and go from deploying to production every 6 weeks to do it 5+ times a day with fewer […]

By: Why I Moved from Protractor to Cypress and the 7 Steps to Cypress E2E Testing Success – Christian Lüdemann

Wed, 03 Jul 2019 18:14:20 +0000

[…] Create a testing strategy (how much of each test type? how does testing fit in the delivery process?) […]

By: The Three Building Blocks of Elite Angular Teams – Christian Lüdemann

The Three Building Blocks of Elite Angular Teams – Christian Lüdemann — Tue, 14 May 2019 17:02:29 +0000

[…] More efficient release processes […]

By: How to Implement Continuous Delivery in Highly Regulated Companies – Christian Lüdemann IT

Tue, 26 Feb 2019 18:01:28 +0000

[…] First, you should start by doing a risk analysis of your system to identify the critical parts, which helps you determine which delivery process would be appropriate for the different system parts. The parts that don’t have a big consequence in case of failure, should be able to be deployed many times daily just like in an unregulated company. These parts include the front end apps (excluding login pages) and non-critical back-end code. You want to make sure that these parts are decoupled from the more risky parts, which will enable you to jump right into implementing continuous delivery. […]

By: Angular Automation: 6 Things That Should Be Automated in Enterprices – Christian Lüdemann IT

Tue, 29 Jan 2019 18:01:12 +0000

[…] You sure you have heard this a lot of times, Having a fully automated delivery process means that every one can release to production on the team (given they have got an approved pull request). The best teams I have worked with have also used feature sites and automatic end-to-end tests to making the delivery processes even more automatic and safe. For more on this I recommend reading my blog post on implementing continuous delivery. […]

By: End-to-end Testing With Protractor: A Pragmatic Guide to Get Started In Your Team – Christian Lüdemann IT

Sun, 25 Nov 2018 19:29:45 +0000

[…] my recommended procedures check my continuous delivery post, where I recommend creating feature environments for every pull request and do the testing there […]

By: Feature Environments in All Environments – A Guide to Faster Delivery – Christian Lüdemann IT

Sun, 04 Nov 2018 18:00:47 +0000

[…] crisis situations is that they force you to think out of the box. If you have read my post about implementing continuous delivery, you know that I recommend the use of feature environments; an environment containing only a […]

By: Visual Regression Testing with Protractor – Christian Lüdemann IT

Visual Regression Testing with Protractor – Christian Lüdemann IT — Sun, 14 Oct 2018 17:01:59 +0000

[…] a lot with DevOps and automation along with Angular development. One of the core principles in Continuous Delivery is having your back covered with automatic testing. Without this automatization in place, you are […]

By: How to use Feature Toggling in Angular Apps – Christian Lüdemann IT

How to use Feature Toggling in Angular Apps – Christian Lüdemann IT — Sun, 26 Aug 2018 18:02:55 +0000

[…] such as experimenting with split tests, open up features for test users, release toggles used in implementing continuous delivery as well as permanent maintenance toggles for disabling certain features eg. if the server is […]