Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement new build and release process #16887

Open
howardjohn opened this issue Sep 6, 2019 · 0 comments

Comments

@howardjohn
Copy link
Member

commented Sep 6, 2019

Design Doc

This bug tracks effort to implement the above design to rework our build and release process.

TODO:

  • Implement new split build+publish process, written in Go instead of bash scripts.
  • Create a new repo, istio/release, to house the implementation and pipeline for daily/official releases
  • Set up daily builds. Implementation: Set up a periodical that builds the release and pushes to GCS bucket istio-release/daily/version. At the end of the job, trigger a PR in the release pipeline. This will run the full suite of tests, using the published binaries. These merge without approval. In postsubmit, the images will be published to gcr.io/istio-release.
  • Set up support for official releases. Not yet clear the exact process that would be, because ideally we have three steps: build the binary, test the binary, then push the binary (to staging repo only!!!). Then after manual qualification, we do the full publish to official dockerhub+github. Perhaps the first step of building the binary could be manual/manual triggered prow job

Related issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.