Description
This apparently happens often at the end of month, and I think this is bad, because we may easily have no CI feeback for FreeBSD for days (or even weeks, if the amount of pushes increases). So unless somebody would pay for a compute limit increase, maybe we should stop running CirrusCI for every push, but instead have nightly runs, and a way to manually trigger the workflow in cases where it seems relevant. I don't know if that's possible, though.
cc @devnexen
Description
This apparently happens often at the end of month, and I think this is bad, because we may easily have no CI feeback for FreeBSD for days (or even weeks, if the amount of pushes increases). So unless somebody would pay for a compute limit increase, maybe we should stop running CirrusCI for every push, but instead have nightly runs, and a way to manually trigger the workflow in cases where it seems relevant. I don't know if that's possible, though.
cc @devnexen