Github actions marketplace, should allow different channels to add the last steps for publication to different registries.
Tools wide enough might be a challenge, but if you already build your package through code or configuratión you just need a compatible action.
Bazel might be general enough to compile any language, in an incremental and effective way. This could happen in the requester's computer, a bigger infra, or just using build resources in github.
So recapping:
Ideally as a dev
We are saying that:
One adds a docker image
And an automáted build process
Goes into the marketplace, gets a general build plugin, selects distribución channels or accepts the default and voila
He's left with development only flows
Meanwhile first requester's in any distribución channel contribute to the registro and end up verifying QAing the final builds (should not be a problem as everything is dockerized and using reliable build systems)
Github actions marketplace, should allow different channels to add the last steps for publication to different registries.
Tools wide enough might be a challenge, but if you already build your package through code or configuratión you just need a compatible action.
Bazel might be general enough to compile any language, in an incremental and effective way. This could happen in the requester's computer, a bigger infra, or just using build resources in github.
So recapping:
Ideally as a dev
We are saying that:
One adds a docker image
And an automáted build process
Goes into the marketplace, gets a general build plugin, selects distribución channels or accepts the default and voila
He's left with development only flows
Meanwhile first requester's in any distribución channel contribute to the registro and end up verifying QAing the final builds (should not be a problem as everything is dockerized and using reliable build systems)