Projectfile CI Resolver | Projectsgenerates near-identical workflows for Github and Forgejo from one agnostic definition.

Projectfile CI Resolver

Origin

I needed something to unify local pipelines in makefiles with CI, and I had Projectfile specification. So, I made a special kind of bridge that generates Github/Forgejo workflows from abstract DAG stored in Projectfile.

What it does

  • generates near-identical workflows for Github and Forgejo from one agnostic definition.
  • same definitions used by M6E makefile framework, you get predictable behaviour locally and in CI
  • in a nutshell, it's portable CI pipelines that could work anywhere

What's next

  • support for Tekton
  • support for Bitbucket
  • support for Gitlab
  • support for Woodpecker
  • support for Jenkins (probably)

It's for you if

  • if you want portability in your pipelines
  • if you have multiforge configuration
  • if you have huge fleet of projects (mass management, support for fleet-wide includes and libraries)

Related