azure devops Use Active Directory Groups in your unified classic CI/CD pipelines Simplify the pipeline security using Active Directory (AD) groups
azure devops Searching for common nodes across area paths Let us assume that you have a common node, for example architecture runway, in a number of Azure DevOps area paths. A common question in such a setup is "what are all the
devops Here's a list of my opensource.com articles We have shared insights into the mysterious DevOps mindset.
azure devops The clash of Azure DevOps Kanban fields and Shared Area Paths Azure Boards Kanban fields are powerful and valuable. Used in the land of shared Area Paths they can, however, introduce inconsistency and confusion. UPDATED: 2018.08.15Let us explore a simple example We
devops Should we use npm audit, Whitesource Bolt, Whitesource, and/or other products? Remember, products enable people - there are no silver bullets!
azure devops Skip Release Notes when re-deploying a release We overwrite the good release notes with the now empty release notes. Not cool!
azure devops One CI/CD pipeline to rule them all I have a dream for one continuous integration and deployment pipeline.
azure devops Auto-generating release notes in Azure DevOps pipelines It’s about continuously learning, adapting, improving, sharing knowledge, and raising the quality bar. Quality in, quality out!
azure devops New and other interesting blogger homes Please update your bookmarks to the new and interesting channels.
azure devops I have a dream of a single build to create simple and effective pipelines My dream is to have one build definition, one build environment, and one build artifact that is deployed to multiple environments by shifting the configuration right.
azure devops Shift LEFT and RIGHT to take yourself off the humbling 2AM calls The 2AM wake up call is the best motivation for a production ready mindset.
meetup Why I dumped agent 77 @ the DevOps Victoria meetup After a parody of hiccups I landed on the other side of the pond
devops Poke the brain on a stick chat - with Mathew Mathai The name of our chat series is based on my colleague Charles K's quote from the 90's, that he would like to have our brains on a stick for projects.
devops Spoiler alert - a sneak peek at some of our DevOps quick poll trends Here are a few sneak peaks into some of the quick poll trends.
devops Feature Flag Manifesto mentioned at Vancouver meetup We're calling the recommendations our FF Manifesto. It's the engineering friendly term for technical governance.
devops Loved the DevOps Vancouver Meetup January 2019 Great sessions including Entropy in DevOps Teams, the Virtues of Being T-shaped, and Progressive Exposure Using Feature Flags:
devops Poke the brain on a stick chat - with Brent Reed The name of our poke-the-brain-on-a-stick series is based on my colleague Charles K's quote from the 90's. He always said that he would like to have our brains on a stick for projects.
devops Is automation really needed for a healthy DevOps environment? Is automation a lifeline and light in the darkness of manual repetition and the pressure to continuously produce and deliver value?
azure devops Visualise work item dependencies in Azure DevOps ... or not After teams have created a few dozen or even hundreds of dependencies it’s important to visualize them.
devops Why don't we nurture our DevOps teams as professional sports teams do? We often wonder why we do not build and nurture engineering teams the same way as professional sports teams - it's unusual to see a team that wins their league pack up and re-group with a new team in the new season.
devops Poke the DevOps Hornet's nest supporting polls and articles THANK YOU for helping us gather the facts from the real-world.
Can collaboration and context switching coexist? An Agile mindset thrives on the benefits of collaboration, cross-functional teams that work jointly, and everyone involved in the project. Collaboration breaks down silos, promotes face-to-face communication, and builds trust. Feature teams get
devops Poking the DevOps hornet’s nest! Our journey is not about technology and products, which are volatile and well covered in product documentation and other books. Instead, our focus is on people and process, and to poke the DevOps hornet’s nest.