We’ve (finally) managed to add support for measuring CICD usage across user/organization accounts. When designing it, we put focus on a generic implementation, so we can measure the use of Forgejo Actions and any external CI engine that is connected to the platform (in our case Crow CI) in a single view.
On the technical side this works through a new API endpoint in Forgejo that accepts information about a finished CI job. The effective usage is then added to the resource tracker under the account which triggered the job.
We’ve decided to start with a budget of 2500 minutes per month per account. This is 25% more than what GitHub offers (2000) and ~ 6x more than GitLab (400). In addition, our runners are much faster (see our hardware sheet) and offer up to 7GB of memory. Jobs are tracked using seconds and not rounded up, so a job that ran 45s is tracked as 45 seconds.
The dashboard provides a clear overview of where and when your budget was spent. You’ll notice that it specifically states “Linux” as the OS the jobs ran on. Given the importance of Windows and macOS runners for some projects (certain (binary) build operations can only built on native runners), we are actively researching how we can provide such runners within the platform without breaking the bank. We can’t promise anything right now and we’ll also surely need support from the community for that, but nothing is impossible!
What to do when the quota has been reached?
We don’t have an automatic subscription/tier system (yet), and neither a fixed per runner minute. If you run out of minutes and don’t want to wait until the next month has started, please contact us via mail or a private forum message and we can increase your quota against a “fair” donation.
We will come up with a transparent pricing for additional CI minutes in the near future!
