Coding guidelines and software quality
We work according to coding guidelines and use tests in our build chain to ensure that these are adhered to. This leads to clearer projects and better code.
In addition to static code analysis and linters, we have test suites in place to ensure that the code we produce works and interacts with other components.
Because we automate these tests during build and deployment, we can very quickly detect if something breaks elsewhere during development - before the code makes it to the production environment.
And deliver it please!
Only when we have our code on the target server and everything works, our work is done. Delivering our software to a server is what we call deployment. On the target server, we only want to have software components that are really in use and needed there. By building our application in the build chain, we can copy the result - the finished application - to the target system through simple network protocols that exist on every server. It is obvious to automate the deployment as well. And of course, we did that too, integrating this process into our build chain.
That sounds pretty complicated? At first glance: yes. But let's take a small step back and look at what we have already achieved so far:
We can restore any state of the project from the past, download all components in the version they existed at that time, assemble them and deliver them to any server. Automated.