Same same but different but still the same.

Month 3, week 2 started with more setting up of the GitLab CI environment. This has been somewhat of a daunting task; not because of the metaphorical documentation that is abundant in DevOps, nor is it due to how complicated the system is, no all that is quite fine. What makes this process painstaking is that the commands don't perform the same way, or at all sometimes, as they would in a regular terminal. So the conclusion is that the scripts need to be written in a way that assumes a perfect run each time. If there is a failure at some point it needs to fail before it has the opportunity to mess up future jobs in the pipeline, and that wouldn't be so bad... if conditional statements would work as intended. Another part of this process has obviously been debugging, and good practice for debugging states to make a few changes as possible in-between tests because if you go and change to much and the problem is fixed then what part actually fixed it or is the problem hiding? So, in order to follow good practice I make few changes, and then I push, it runs the pipeline and I make the necessary fixes and repeat. Pushing up to GitLab does take a bit longer than hitting build in Visual Studio so this can sometimes cause some frustration.
Overall, GitLab has been a thrilling learning experience and my command line knowledge has increased by a substantial amount, this, I am thankful for because it was a skill I was sorely lacking up until this point. Though it can be frustrating at times, what part of development isn't? Being able to stay calm and know what to do next in order to get the job done is a skill that is being exercised aggressively in Gateware and that too, I am thankful for.