After upgrading to the newest version of TeamCity and enabling native git, roughly half of our builds just immediately failed with an error. Here's the solution.
We loathe downtime and failing services. We always often talk about how we can keep our code stable. How we can avoid instability. However, certain types of instability should be embraced.
Working with Backstage.io in a local development environment, can often be made a lot easier by simply removing authentication. Here's how to simplify development, while keeping your production instance secure.
While importing components into Backstage, you may encounter a NotAllowedError telling you that "Entity [...] is not of an allowed kind for that location". Here's how to fix it.
You've just migrated to Cake for building your freshly upgraded NUnit test project, but TeamCity won't run your tests. Here's how to fix it.
Backstage.io is a platform to build developer portals, made by the people over at Spotify. In this post, you'll get a complete guide to setting it up with Azure, Github and Terraform.
Writing code is easy. Dealing with the the wrong dependencies down the line is hard, and can cost hundreds or thousands of hours to clean up when you suddenly need to. Spend time actively managing your dependencies - for any lasting software, this'll save both time, risk and money in the long run.
Through the years, I've stumbled across thousands of lines of unused code of all kinds. It might have been nice, well tested, neatly architected code fitting perfectly into all the tools, frameworks and standards for its time. But in the end, it was never called.