Windows 10: Facing Issues while generating .MSI using YAML code in GitLab Runner which is running on...

Hi All, Good Morning/Evening! As a part of User Story, I need to generate a .MSI out of 3 Projects in .net and facing Issues in GITLAB CI/CD Pipeline. GitLAB CI/CD pipeline will run these 3 Projects in GitLab runner and as we do no have ADMIN privileges for GITLAB, I am facing issues with one of the Project to run one of the project on Linux Docker ContainerGitLab runner. Basically i was looking for Windows Docker Container for GITLAB Runner. As an aletrnate Solution,In Local i was able to do it using Python and generate .MSI but facing issues when i run the same on GITLAB CI/CD Pipeline.

:)

 

Grid Runners

We received the code for Minecraft Grid Runners at Target. We have redeemed at the Microsoft store and it shows up in my account, but when I click "Install" it just shows the 16 digit code and a button that says "copy". When I click copy nothing happens.
No wizard opens or anything that would lead to a next step. Any suggestions?

 

YAML sucks

Written back in 2009, so I guess this fad is still going.

Haven't been exposed to it yet so I took a look at a YAML sample file just now...

Barf.

 

YAML sucks

For those who haven't heard about it, here's the official site for it:
The Official YAML Web Site

Sure, it is a readable format but it is the worst format I've ever worked with in terms of coding for. I tried using other people's libraries (three of them I think) and was so confused, I trashed them. I tried coding my own, also resulted in confusion and trashing it. Finally, I decided the only way I can navigate the all important "spaces" (because they refuse to use tabs) was to use a tree so I could easily tell it to move between children and parents as it was parsing each line. That finally got the hierarchy mess sorted but then, to output the file back in YAML format, I had to write a wall of text because Trees aren't navigator friendly (have to open child after child after child and/or assign new objects to new objects to new objects). Not only that but in order to do the "name: value" at the end, I had to put in some shameful, unflexible wizardry to make it ignore outputting tabs (which breaks the format), not output colons, and ignore linebreaks. It's amazing it works at all.

For the love of the computing gods, use XML, INI, or some other decent scripting format than YAML. They may not be as human ledgible as YAML but editors are relatively easy to make which end up being infinitely better than text editing a YAML anyway.

JSON is better than YAML because it has brackets to tell when something starts and stops. YAML omits almost all of them.