Bug 1277683

Summary:	Split the product-specific plugin (ovirt) from the core (lago)
Product:	[Community] ovirt-system-tests	Reporter:	David Caro <dcaroest>
Component:	RFEs	Assignee:	Yaniv Bronhaim <ybronhei>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	bugs, eedri
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ci
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-27 19:24:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Caro 2015-11-03 20:16:51 UTC

Description of problem:
Right now we have the plugin in the same repo than the core, the issue is that the plugin is highly dependent on the ovirt-sdk and ovirt-setup versions, I think it should be moved inside the same repos those reside (maybe split in two if they don't reside in the same repo) and build and distributed alongside it. That will allow to pair the development of both, and have them changed together in the same patches if needed.

If they reside out of the product repos, any change in the product that requires a change in the plugin will create a situation where:
* if you change the tests before merging the patch:
  - you will break all the other patches tests until you merge
  - once merged all the other patches will have to rebase on top of you patch to pass the tests
* if you merge the patch before changing the tests
  - all the patches rebased on it will fail until the tests are changed
  - once the tests are changed, all the patches will fail unless rebased

while moving the plugins code to the same repo allows you to just change the tests in the same patch and contain the changes there, so no other patches break, and no need to rebase before or after you patch is merged

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 David Caro 2015-11-03 20:18:04 UTC

Worth mentioning that just spliting the plugin from the core repo, does not add any advantage, the key is moving it to the same repo as the product it was meant for.

Comment 2 David Caro 2016-01-27 19:24:54 UTC

I don't think this is never going to happen...