undefined | Better HN

0 pointspjmlp3y ago0 comments

Which means their workforce doesn't give a fuck about supporting CI/CD pipelines used by Windows development, unless they have some mental powers to test them with having Windows around.

0 comments

salzig3y ago

So, you think a very small Modul that communicates via http only, and written in different language then the main project (go instead of Ruby), is a reason that the developers of the main project (ruby, only supported on Linux) should also be able to work on Windows, or even be supported in doing so, cause ~three people need to support the gitlab-ci runner on windows?

Edit: oh, and testing of those gitlab-ci functionalities can easily be done in a VM.

pjmlpOP3y ago

Since when CI/CD products like a compiler, static analysis, os frameworks are a very small module?

If they aren't running Windows, I really doubt their skillset to give any kind of meaningful support.

salzig3y ago

Since when does Gitlab(-CI) Provide a Compiler or OS Framework? Gitlab-CI allows you to execute commands in some form of defined environment (Container based, insite a VM or on bare-metal), They have to make sure the commands are executed in the order you defined, and the output is then shown in the WebUI. Everthing run is "random" cli-tool you "found" somewhere.

1 more reply

j / k navigate · click thread line to collapse

0 comments

salzig3y ago

Edit: oh, and testing of those gitlab-ci functionalities can easily be done in a VM.

pjmlpOP3y ago

Since when CI/CD products like a compiler, static analysis, os frameworks are a very small module?

If they aren't running Windows, I really doubt their skillset to give any kind of meaningful support.

salzig3y ago

1 more reply

j / k navigate · click thread line to collapse