Articles tagged with devops
As a team we want to create an empathetic, safe, and vibrant ecosystem
Let us review two strategies to share scripts and config files with your Azure (YAML) Pipelines.
If we unpack the DevOps DNA we will find a prominent genome labeled O-O-D-A.
Design is not a static construct, it evolves by refactoring as we keep changing the code
Enabling engineering to continuously build, validate, and deploy secure solutions to delight our customers
Summarising the core terminology and lifetime of our pipelines.
The importance of properly securing client-side applications has never been more urgent!
TDD explained to non programmers by using the example of writing a short story
What does 'extreme' in Extreme Programming stand for? It stands for extreme interruptability and extreme steerability
Manage your blast radius through progressive exposure with feature flags
Summarising the main points of our 2nd generation app-type blueprint-based pipelines.
Any system operation we can perform manually can be fully automated by writing scripts
Continuous Deployment is a pivotal ingredient of a healthy DevOps mindset and our ability to delight end-users with continuous value. It is the holy grail of our profession.
Summarising the main points of YAML syntax, within the context of our generic blueprint-based pipelines.
Part 7: Pipelines - There is more! Simplicity and enablement, courtesy of the app-type blueprint-based YAML pipelines
Do you want to own two or seventy five dozen lines of pipeline code per application? The choice is yours!
Extreme programming keeps going strong 25 years after its launch
Programming computers by feeding them plain text is very slow and needs to be sped up.
Visual example illustrating the fundamental differences between incremental and iterative development process.
This post attempts to give our critics some answers and scratch the surface of the possibilities and values of our new blueprint-based pipelines.
Use feature flags to fine-tune each release in production.
Configuring complex workflows that govern Continuous Integration and Continuous Delivery must only be allowed by making changes to the YAML source files; GUI tools must be prohibited
Neither the bootstrap nor generic templates are rocket science, and the YAML-based pipelines are as complex as you make them.
WorkSafeBC DevOps 100th sprint celebration coincided with the 20th anniversary of the Agile Manifesto
Think of blueprints and associated templates as re-usable LEGO blocks, ranging from a bag of "do it yourself" blocks, to complex and detailed kits, such as the Imperial Star Destroyer.
We can use the power of the new multi-stage YAML pipelines to make even our most critical security engineers smile from ear to ear.
With the support from all people, YAML templates support our five (5) core goals and pillars of our common engineering system.
The new Azure DevOps YAML pipelines have been the focus of innovation, enabling engineering to treat pipelines as code.
Pipelines enable engineering to continuously deliver value, map and improve their processes and workflows, promoting consistency and reliability across the organisation.
We need to avoid the infamous 2AM call!
Teams share collective responsibility and therefore collectively own the code