Build servers build: they compile, test code, and create artifacts.
Why are we then making them do much more than that?
Looking at builds in the Power Platform / Dynamics 365 world, some people go full in and even go overboard.
I have seen builds deploying third-party solutions, migrating reference data, configuring (environment) settings and more.
The build becomes an application by itself. Only the DevOps expert can maintain it.
Try to keep things simple, so everyone can understand it.
Power Platform Advisor
Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.
Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).
Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.
Services:
– Strategy and tactics advise
– Automating and integrating
A daily newsletter on automation and eliminating friction
Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...
The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...
Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...