How to screw up CI/CD without really trying

It begins

Yes, I am way behind on writing. RL keeps invading and I spent so much time recently trying to figure out how to create workflows that would showcase my work on an app.

I have a small Java console text adventure game I am working on. The goal is not the game, but the engine and the process of developing software. I am approaching a major point in the development. I am nearly at V1.0. I have someone that is testing the playability of the software. Having just a regular repo isn’t enough anymore. I needed something more robust. So, I started learning some of the things to do with CI/CD ( continuous integration, continuous development ).

Now I understand bloatware

I have not written in a while, which is not good. But, I have been so busy between RL work and my software work that I just have not had the energy or time. When I am at home, I have been working on learning how to package my adventure game. It is not as easy as it looks. I would liked to have written this post as a mini-howto on packaging via jpackage, codeberg, and github. Yeah, it’s not happening yet.

How I write code

I hope two write two posts today. I need to set things up for you all before I dive into code. I don’t know if others call the developer environment they use a stack, but that’s my term.

The reason I do this is that when I learned C#, I used what was good for me. I had Microsoft’s VS Code running on a linux machine with Dotnet Core . I was watching some learning tutorials on YouTube and discovered things didn’t work like the presenter showed them. After much frustration and arguing with the presenter, we both discovered that while I used Dotnet Core and VS Code, he used Microsoft Visual Studio and .NET. The two were not the same, though now they finally are the same. Since then, I am careful to note what I am using so that others will know beforehand.