If you read my last article about the builds (here: http://www.mynavblog.com/2020/06/05/automated-builds-part-9-using-azure-vm/) you know that current one will be a continuation. But since the beginning of June, a lot changed in the builds area, so I needed to rethink the scenario. First, Freddy...
It is quite a while since I posted a series about the automated builds. Those blogs focused on the not complicated pipeline when the agent is self-hosted. If you did not read them, I recommended that you will look at them...
The series I started from creating the container, then showed compiling and publishing the extensions (app files) and finished with executing automated tests. But all happened on the Docker container. Should we use it also for manual tests or production environment?...
I almost get to the end with the series. Today last point related to building pipelines. Sometimes it is needed to store the solution in different repositories – one for each extension. For example, this can happen when the solution is...
I get to the point in the series where I have an app published to the build container. However, I am missing a very important step – testing of the application. Let’s change that and add to the pipeline the automated...
In the series related to the automated builds, I get to the point when I can compile and publish the extension in the docker container. In this article, I will show how to do that. Additionally, in the end, I will...
