Also, would it be possible to grant me the 'system:build-strategy-custom' role?

For CoreOS, I'm working on making CoreOS Assembler a proper custom builder. There's a bunch of really good reasons why (resource utilization, cross-cluster orchestration, multi-arch, pipeline consolidation). I currently have CoreOS assembler running as a custom builder in the Red Hat internal OCP cluster.

@darkmuggle has been added to fedora-coreos admins group and they would also able to see ben-fcos-dev namespace as requested.

about the request from @darkmuggle, I would need to see what kind of access level is this and will discuss this with @dkirwan.
Will post update here

CoreOS today is built using CoreOS Assembler (COSA), which is a container that has all the dependencies and the build logic. We then use Jenkins to orchestrate COSA. We spend an inordinate amount of logic in Groovy to create COSA commands. Worse we end up having a Openshift build config that creates a Jenkins job that then uses Groovy to create pods that run COSA. The whole chain is a bit...brittle.

The reason we are looking at doing a custom build strategy is that the existing strategies does not cover our use case since our output is cloud images. The Jenkins strategy is the default one, but that has led us to our brittleness today. And the docker strategy doesn't work since we are not build Docker images.

'system:build-strategy-custom' role was added to the namespace