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?

Remy van Duijkeren

Remy van Duijkeren

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

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Cancel Culture in IT

Cancel Culture in IT Cancel Culture is happening in major communities to developers and contributors, like: Linux Kernel C++ Standard Committee Python NixOS openSUSE Godot And the reasons? Completely absurd: Being Republican Liking an old SNL sketch Using the word...

read more

VS Code is NOT an IDE.

VS Code is NOT an IDE. And I like it that way. I use VS Code as a fast text editor. Just a couple of bare-bone plugins. No bloat. No unnecessary features. Just speed. I see people turning VS Code into a full-fledged IDE with tons of extensions. At that point… just use...

read more