basysKom Toolbox

09 – Proper automated builds

Proper automated builds


Be able to reliably create a new build of your project.


Builds that take a lot of manual work are highly error-prone. Make sure to have a good foundation for your project by implementing automated project builds. Having automatic – one-stop – builds is a baseline effort to enable other, high-value tools such as continuous integration, unit tests or just easy on-boarding of new project members.

It should be possible to check out a project from VCS and create a build with just 2-3 commands.

A strongly related topic is how to handle external dependencies and build environments.





Implementation effort

Minimal for new projects. Potentially substantial for large existing projects.




  • Do not rely on the project files of IDEs for your builds. These are hard to automate, bad for version control and force all team members into the same IDE. Also there is a tendency of projects to outlive their initial IDE, creating a porting effort down the line.

See also

Implementation hints

  • Consider to use a package manager like or vpkg to manage dependencies.
About the Toolbox

The basysKom Toolbox is a state-of-the-art collection of best practices in agile management and software development and a valuable tool for every kickoff meeting.

These cards can be used during a project kickoff in order to select best fitting good practices from the very start of your project, but also as a reminder during the course of a project implementation. Every card holds a QR code with additional information related to the specific tool, the tools’ applicability, known constraints and additional tips on how to implement it in a project setup.

You can provide us feedback on GitHub.


basysKom Newsletter

We collect only the data you enter in this form (no IP address or information that can be derived from it). The collected data is only used in order to send you our regular newsletters, from which you can unsubscribe at any point using the link at the bottom of each newsletter. We will retain this information until you ask us to delete it permanently. For more information about our privacy policy, read Privacy Policy