-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Start instructions for creating a release #298
Conversation
* Define the default values for the componet in the component library. * Make buildTemplate a local variable so it inherits context automatically.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @lluunn |
The workflow for building the TF serving image didn't even seem to run the checkout step. Lets try rerunning. /test all |
/test all |
I did
Error is
Looks like maybe a bad merge. |
Review status: 0 of 10 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. releasing.md, line 24 at r4 (raw file):
should cd to the workflow dir? Comments from Reviewable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one comment. Looks good, thanks!
Review status: 0 of 10 files reviewed at latest revision, 1 unresolved discussion. releasing.md, line 24 at r4 (raw file): Previously, lluunn (Lun-Kai Hsu) wrote…
Done. Comments from Reviewable |
…#298) * Added an environment variable to central dash to target the correct KFAM target * Addresed PR comments and updated tests
Start putting instructions together for how one could release Kubeflow.
The instructions are rather adhoc and reflect what one could do today
They do not reflect what we think our release process should look like.
The current instructions only cover building and releasing TFJob operator and the TFServing images
Refactor the TFServing image E2E workflow so we can use it to build release images
registry
large so I think it makes sense to pass them as a dictionary and not as a list of arguments
and don't have to pass a bunch of arguments every time we build it.
Update the actual image used by TFSerivng to the newly built image.
@willb and some others are putting together a proposal for our release process. Hopefully this PR will help inform that work and help us figure out how to iterate.
Related to Create a minimal release process for our ksonnet configs #215
This change is