-
Notifications
You must be signed in to change notification settings - Fork 996
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
Add CI for feature server Docker image #1925
Add CI for feature server Docker image #1925
Conversation
e28d4be
to
077a39e
Compare
Codecov Report
@@ Coverage Diff @@
## master #1925 +/- ##
==========================================
- Coverage 82.34% 81.96% -0.39%
==========================================
Files 96 96
Lines 7490 7557 +67
==========================================
+ Hits 6168 6194 +26
- Misses 1322 1363 +41
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
6d4d548
to
0f02210
Compare
Signed-off-by: Felix Wang <wangfelix98@gmail.com>
0f02210
to
2941bf7
Compare
/kind housekeeping |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: achals, felixwang9817 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 |
@felixwang9817 you can also use your own repo if you just want to iterate quickly without actually going through a PR flow. |
Signed-off-by: Felix Wang <wangfelix98@gmail.com>
New changes are detected. LGTM label has been removed. |
Lgtm. Retried integration tests. |
Signed-off-by: Felix Wang wangfelix98@gmail.com
What this PR does / why we need it: This PR is adding CI for building the feature server Docker image. Since the workflow cannot be tested in this PR, I will iterate on the workflow in later PRs.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: