Issues 38 open · 61 closed

● #59 Environments: deployments, protection and an environment claim

opened 20 days ago by andymccall · 1 comment

● #58 Artifacts between jobs in a run

opened 20 days ago by andymccall · 1 comment

● #57 Approval gates: a job that waits for a person

opened 20 days ago by andymccall · 1 comment

● #55 Allow-listed egress for jobs (network "egress")

opened 20 days ago by andymccall · 2 comments

● #38 Jetstream: the fleet as a service of its own (design) feature

opened 24 days ago by andymccall

● #36 Runner capabilities and placement: architecture, tier, speed and load (spec §11) feature

opened 1 month ago by andymccall

● #35 Metrics: time to launch, queue time, run time, runner use featureflow-next

opened 1 month ago by andymccall · 1 comment

● #34 A message queue between hub and runners featureflow-next

opened 1 month ago by andymccall

● #33 Run anywhere: cloud and Kubernetes runners behind one abstraction; jobs that move featureflow-next

opened 1 month ago by andymccall · 1 comment

● #29 Fan-out: a matrix, and test sharding featureflow-next

opened 1 month ago by andymccall

● #26 Outputs: globs and directories; a publish step that attaches to a release featureflow-next

opened 1 month ago by andymccall

● #25 Images built in Flow and fetched by runners from the hub featureflow-next

opened 1 month ago by andymccall

● #21 flow-casfs: a read-only FUSE mount of a state (P5a)

opened 1 month ago by andymccall · 1 comment