Doing commits on the Build Server?

by Jan 30, 2023

Are you doing commits on the build server?

When doing ALM on the Power Platform / Dynamics 365, I often see builds doing commits on the Build Server.

This is not a good idea.

Build servers build: they compile, test code, and create artifacts.

Doing commits on the build server makes it harder to track the exact source code used to create a particular build. It can lead to issues with the integrity and reproducibility of the build process.

Also, a build server starts a build when a commit is done, so you could end up in an endless loop. You need to add extra complexity to your build to counter this.

Try to do all the commits before you build on the build server.

What is your view on this? Are you OK with doing commits on the build server?

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Improving Optimization?

Improving Optimization? The traditional steps of Optimization: 1. Eliminate 2. Automate or 3. Delegate What if we added a missing element? Simplify. Before automating a convoluted workflow or delegating a tangled task, strip away the unnecessary. Make processes leaner...

read more

Unit tests for Dataverse plugins?

Unit tests for Dataverse plugins? I must admit, I almost never write unit tests for Dataverse plugins. Plugins are often quite simple, testing them in isolation is not particularly useful. Often you only test a couple of if-statements. Unit tests don't bring a lot of...

read more

New Dynamics 365 browser extension

New Dynamics 365 browser extension I'm trying out the new -Power Roles- extension and it looks very promising. You browse to a Dynamics 365 (or Power Apps) app and then you press -record-. It will then monitor all the action you do in the app and propose which...

read more