-
Notifications
You must be signed in to change notification settings - Fork 10
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
[#714] Fixed filters and model deploy #724
Conversation
06bfa21
to
ef23443
Compare
bot, test all |
Can one of the admins verify this patch? |
1 similar comment
Can one of the admins verify this patch? |
bot, test all |
Build status: FAILURE |
b9129cc
to
b5b495d
Compare
Build status: FAILURE |
bot, test all |
Build status: FAILURE |
bot, test all |
bot, test app |
Build status: FAILURE |
bot, test all |
Build status: FAILURE |
bot, test all |
Build status: FAILURE |
bot, test all |
f5478c1
to
30582f9
Compare
bot, test all |
Build status: FAILURE |
bot, test all |
Build status: FAILURE |
bot, test all |
Build status: FAILURE |
bot, test all |
Build status: FAILURE |
bot, test all |
Build status: SUCCESS |
e58b9d6
to
d740c30
Compare
bot, test all |
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.
👎
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.
👍 taking into account #736
* Check that model already deployed by model id and version despite of image docker name. * Move filters by model id and version on the kubernetes side.
d740c30
to
ae11290
Compare
Build status: FAILURE |
bot, test all |
1 similar comment
bot, test all |
Build status: FAILURE |
Build status: SUCCESS |
image docker name.
This fixes the comment #714 (comment)