Currently running Jenkins but kind of hate it and every three months or so I start googling alternatives until I feel that it _does_ actually do what we need and I don't feel like setting up something new that's probably just as horrible.

Having a look at TeamCity though and it does seem to check a lot of the right boxes. What say ye? Yay? Nay?

#softwareengineering #BuildAutomation #ci #teamcity #jetbrains

Finally done adding initial support for #macOS (via home-manager) to the #nix configuration of #JetBrains #TeamCity build agents: https://gitlab.com/framebunker/framebunker.Nix.BuildAgent

Still requires manually running an install step when adding an agent, but certainly beats messing around with git & Java versions, rediscovering agent config requirements, etc.

#NixOS

Finally got around to sharing this: https://gitlab.com/framebunker/framebunker.Nix.BuildAgent

It's the ingredients needed to form a shake & bake TeamCity build agent with optional support for:
- mono & .net core.
- AppCenter.
- Unity.

Based on NixOS, post-install maintenance is _very_ manageable. Minor TODOs remaining, but this is what we're running.

#teamcity #dotnet #appcenter #unity3d #ci #nixos

I have finally gotten my #TeamCity workflow smoothed out to the point that I can be confident that pushing code will publish a #NuGet I can access in another project in 60 seconds or less.

Not bad for my first big #SelfHosted #HomeLab project

To bootstrap my #homelab infra, I hope to have #teamcity building and publishing its own worker agents.

Apparently there are no first-party agents that support #dotnet builds, so I'm adding mono to the official source.

Its pretty cool that #gitea can act as a personal package repository for both nugets and #docker containers

I'm not sure I will go as far as to have teamcity DEPLOY its own agents, but having them in a docker repo is a great start

Does anyone else here self-host CI/CD tools?

I recently managed to get a pipeline running on each push to my master branch. Commits to #gitea trigger #TeamCity to build the project, run tests, package my #DotNet nugets, then publish them back to a gitea repository I can reach from my IDE.

I'm pretty pleased with it. I'm wishing for something a little more open source than team city though.

Ideas? Experiences?

TIL:
- #Unity will ignore the -executeMethod flag when the -runEditorTests flag is also passed.

- The #TeamCity #Unity runner will always pass the -quit flag to Unity when configured for -executeMethod, so good luck programmatically running your tests that way.

- The #Unity test runner _does_ wait for completion of other domain load invokes, including invoked script reloads, before responding to -executeMethod.

So: If you want to parameterise a TC Unity test run, use custom CLI parameters.

Is #TeamCity still a CI/CD viable option if it keeps ignoring basic #security #best-practises like #ED25519 #SSH #keys in 2021?

https://youtrack.jetbrains.com/issue/TW-47419

...und #microsoft setzt #teamcity ein? Ernsthaft? Wieviel Fehlannahmen stecken in den obigen Sätzen? Das muss doch auch #heise erkennen das da nur Mist drinsteht und man diesen US Bullshit (Naivität wird oft mit Dummheit verwechselt) nicht nachplappern sollte bevor es nicht einigermaßen sichere Beweise für solche Behauptungen gibt (und die dürften nicht mal in 10 min. Forensik bestehen).