search

product-os / flowzone

Reusable, opinionated, zero-conf workflows for GitHub actions
https://flowzone.pages.dev
Apache License 2.0
15 stars 5 forks source link

GitHub (balena) self-hosted runners (re)homing #207

Open ab77 opened 2 years ago

ab77 commented 2 years ago

Currently they live in an obscure location.

Should we re-home them to this repository and build the block(s) or give them a separate home (i.e. balenablocks/flowzone)?

After that we can add the block to existing Jenkins and resinCI fleets, since we have compute power there already.

klutchell commented 2 years ago

I think they should have their own repo under the product-os GH org (not attached to Flowzone or resinCI).

They shouldn't be added to the balenablocks org for a few reasons:

  1. Our GH orgs are based on loops, not application types (or that is the intent anyway)
  2. Following the above, balenablocks repos may be moving to balenalabs soon (cc @nucleardreamer )
  3. balenaCloud orgs support all application types, there is no reason to put all blocks in one org, and all fleets in another

So we should use Flowzone to build the product-os GH runners and deploy them to a product-os block.