Closed freynca closed 6 years ago
Since the sk8s repo is public and PRs can include code from 3rd parties, we need to be a little careful with auto-Ci for PRs.
I updated the story to include helm-based PR workflow.
@freynca what was the reasoning for using a dedicated bucket / helm repo for PRs?
@jldec For clear separation of pre-release / test artifacts, and final artifacts. Kubo uses a similar model.
@freynca - I don't believe we have enough info today to decide that there will be exactly 2 categories of artifact (final and test)
Unless there is some other argument, i'd prefer to start with the opposite assumption - use one repo for all releases, and only split things out if/when necessary.
Closing as redundant.
As a sk8s developer, when i'm working on a PR, i should be able to run Ci on that PR. I should also be able to use the helm chart for a PR to deploy the bits onto my own cluster (or minikube).
Create a pipeline to build sk8s PRs; integrate with GitHub.