-
Notifications
You must be signed in to change notification settings - Fork 135
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
update the kfp release process #338
Conversation
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.
LGTM
kfp/kfp_ray_components/Makefile
Outdated
$(MAKE) set-versions | ||
$(MAKE) .lib-src-image | ||
|
||
|
||
.PHONY: .reconcile-requirements | ||
.reconcile-requirements: | ||
@$(make) .setImage |
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.
Is there a diff between $(make)
and $(MAKE)
?
kfp/kfp_ray_components/Makefile
Outdated
@$(make) build | ||
$(MAKE) .defaults.publish-image | ||
ifeq ($(CURRENT_KFPv2), 1) | ||
export KFPv2=CURRENT_KFPv2 |
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.
mabye run set-versions
again here
c297f87
to
70fdac7
Compare
Signed-off-by: Alexey Roytman <[email protected]>
Signed-off-by: Mohammad Nassar <[email protected]>
Signed-off-by: Alexey Roytman <[email protected]>
Signed-off-by: Alexey Roytman <[email protected]>
Why are these changes needed?
Update the KFP publishing process. We have to publish 2 different images: one for KFPv1 and another for KFPv2.
Note: this PR is instead of #335