For a few months we've been using TeamCity for our CI. It's fine, but it's extremely different from almost any other CI solution. It's kind of a pain to maintain because it's outside of the repo, uses Kotlin as the configuration language, and doesn't integrate natively with Codeberg (although I did get something to work, there). It also has odd pricing where it's billed by the number of distinct committers to a codebase with a minimum of 3.
However Codeberg offers CI hosting for project with open-source licenses. They run a Woodpecker service which is similar to other CI solutions. That's what I'm switching to, here.
Another nice benefit of the CI is that the runs are public, so y'all reviewing PRs can actually see why something failed if you want to.
For a few months we've been using [TeamCity](https://www.jetbrains.com/teamcity/) for our CI. It's fine, but it's extremely different from almost any other CI solution. It's kind of a pain to maintain because it's outside of the repo, uses Kotlin as the configuration language, and doesn't integrate natively with Codeberg (although I did get something to work, there). It also has odd pricing where it's [billed by the number of distinct committers](https://www.jetbrains.com/teamcity/buy/?edition=cloud) to a codebase with a minimum of 3.
However [Codeberg offers CI hosting](https://docs.codeberg.org/ci/) for project with open-source licenses. They run a [Woodpecker](https://woodpecker-ci.org) service which is similar to other CI solutions. That's what I'm switching to, here.
Another nice benefit of the CI is that the runs are public, so y'all reviewing PRs can actually see why something failed if you want to.