[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility

Barak Korren (oVirt JIRA) jira at ovirt-jira.atlassian.net
Thu Nov 16 13:14:34 UTC 2017


    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35348#comment-35348 ] 

Barak Korren commented on OVIRT-1769:
-------------------------------------

You can`t run a '*-4.1' suit on 'master' code, the final part of the suit name determines which code it tests... instead I new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like 'compat-suit-master'

> run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
> -----------------------------------------------------------------------------------
>
>                 Key: OVIRT-1769
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: OST
>            Reporter: danken
>            Assignee: infra
>            Priority: High
>
> starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project.
> However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100071)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20171116/d37be7fc/attachment.html>


More information about the Infra mailing list