caicloud / nirvana

60%

master: 46%

LAST BUILD ON BRANCH v0.1.0

branch: v0.1.0

CHANGE BRANCH

x

Reset

• v0.1.0
• Jimexist-patch-1
• add-landscape-badge
• add-linter
• fix-builder
• master
• plugins
• pr/115
• release-0.1
• release-0.2
• release-0.3
• release-1.0
• revert-342-handler
• revert-358-cherry-pick-342-to-release-0.2
• v0.1.0-alpha.0
• v0.1.0-alpha.1
• v0.1.0-alpha.2
• v0.1.0-beta.0
• v0.2.0
• v0.2.0-alpha.0
• v0.2.0-alpha.1
• v0.2.0-alpha.2
• v0.2.1
• v0.2.10
• v0.2.2
• v0.2.3
• v0.2.4
• v0.2.5
• v0.2.6
• v0.2.7
• v0.2.8
• v0.2.9
• v0.3.0-alpha.1
• v1.0.0-alpha.0

Build # 599

Build Type

push

travis-ci

Committed by caicloud-bot

Commit Message

fix(service): Consumes and Produces of descriptor should affect current definitions (#201)

Automatic merge from submit-queue.

fix(service): Consumes and Produces of descriptor should affect current definitions

**What this PR does / why we need it**:

Descriptor's Consumes and Produces can't impact its definitions.

**Which issue(s) this PR fixes** *(optional, close the issue(s) when PR gets merged)*:

Fixes #

**Special notes for your reviewer**:

/cc @yejiayu 

**Release note**:


```release-note
NONE
```

<!--  Thanks for sending a pull request! Here are some tips:

1. https://github.com/caicloud/engineering/blob/master/docs/review_conventions.md  <-- what is the review process looks like
2. https://github.com/caicloud/engineering/blob/master/docs/commit_conventions.md  <-- how to structure your git commit
3. https://github.com/caicloud/engineering/blob/master/docs/caicloud_bot.md        <-- how to work with caicloud bot

Other tips from Kubernetes cmomunity:

1. If this is your first time, read our contributor guidelines https://git.k8s.io/community/contributors/devel/pull-requests.md#the-pr-submit-process and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
2. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/devel/pull-requests.md#best-practices-for-faster-reviews
3. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/devel/pull-requests.md#write-release-notes-if-needed
4. If the PR is unfinished, see how to mark it: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#marking-unfinished-pull-requests
-->

Run Details

3207 of 5382 relevant lines covered (59.59%)

72.17 hits per line