Skip to content
CodeFloe
Git

CI/CD

As CodeFloe has a strong focus on automation of any sort itself, providing sophisticated CI/CD solutions to its users is a must.

CodeFloe does not offer just a single CI/CD solution (which for other services is usually bound to their platform exclusively), but two services, of which one is even forge-agnostic, i.e. it can be connected to other Git forges without the need to change workflows.

Choose Your CI/CD Solution

Section titled “Choose Your CI/CD Solution”

It is up to you which one to choose:

  • Crow CI - An independent, centrally administrated CI/CD solution developed and maintained by the people driving CodeFloe
  • Forgejo Actions - Integrated into the platform and configured on a per-repo basis, following GitHub Actions

Key Differences

Section titled “Key Differences”

Both have fundamental design differences:

  • Crow CI comes with a UI that integrates all settings and repos into a single dashboard
  • Forgejo Actions is directly integrated into the Forgejo UI and only has a minimal UI to view workflow logs

Forgejo Actions relies heavily on the use of predefined actions (aiming to simplify repetitive tasks), which require a full NodeJS runtime. This is also the reason why every build environment that should support the use of “actions” is based on a node image.

Crow supports “plugins” which are similar to “actions”. These can be written in any language as long as they are called through an (immutable) entrypoint in a container image.

Additional Topics

Section titled “Additional Topics”