Comment by avtar
7 months ago
It would be great if Actions received some polish. How are people applying org/team wide policies such as job timeouts to avoid burning through monthly limits? Last I checked this wasn’t a feature :/
7 months ago
It would be great if Actions received some polish. How are people applying org/team wide policies such as job timeouts to avoid burning through monthly limits? Last I checked this wasn’t a feature :/
You can draft up your own json schema and apply it as a validation check when PRs are created. Or just use a proper programming language for the yaml checks.
You can pair that up with a template repository for the org and everyone can start new projects from that template (which contains the workflow to check future workflow files).
If you want assistance with organisation-wide code policies, I can help and my email is in my profile.
Templates and config checks are what I ended up with but it would be nice if this was enforceable out of the box. This was just one example that came to mind where the experience feels rough requiring workarounds https://github.com/orgs/community/discussions/14834 Perhaps it's case of grass being greener elsewhere and my patchy memory but I'm almost missing Jenkins...