Articles tagged with pipelines
Solving the pipeline-as-code "chicken or the egg" challenge by suppressing selected logic
The use of TLAs creates subpar collaboration, unnecessary confusion, and unintended waste.
Let us review two strategies to share scripts and config files with your Azure (YAML) Pipelines.
Our quest for continuous improvement, simplicity, consistency, enablement, and automation has taken us into a realm of Azure Pipelines that amaze even our most critical engineers.
Understanding and avoiding gotchas that may keep you up at 2AM, troubleshooting YAML-based Azure Pipelines
Automate a “hello world in less than 1min”, also referred to as our “walking skeleton”.
Enabling engineering to continuously build, validate, and deploy secure solutions to delight our customers
Summarising the core terminology and lifetime of our pipelines.
Summarising the main points of our 2nd generation app-type blueprint-based pipelines.
Snippets of common questions and issues from Azure Pipeline workshops and support calls. Today's snippet includes conditionals, parameters, and triggers.
As per documentation, output variables can be used across stages in an Azure YAML-based pipeline. I will share a few turbulent moments we experienced while troubleshooting this feature in one of our pipeline blueprints.
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!
This post attempts to give our critics some answers and scratch the surface of the possibilities and values of our new blueprint-based pipelines.
How to find more information on hosted Azure DevOps agents, such as capabilities and IP addresses.
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.
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.
Closer look into the principle of least knowledge
Instead of managing permissions for users in Azure DevOps, we use Azure Active Directory groups to fine tune permissions
Simple isn't easy, but it is the only way to build anti-fragile systems
The longer the wait to deploy, the bigger the risk of things going south
Developing a feature without formulating a hypothesis is like shooting in the dark
Change is stressful and risky, but avoing it is even riskier