Red Hat Bugzilla – Bug 1015243
Test latest domain configuration against previous versions of EAP
Last modified: 2015-11-24 06:06:38 EST
This is necessary to be able to test interoperatbility of a EAP 6.2 DC running EAP 6.0.x and 6.1.x slaves.
This is big effort, already in late tests execution phase (waiting for ER5), targeting for test development phase for EAP 6.3.
The work has already been done. It lives here: https://github.com/jbossas/jboss-eap/pull/510.
Brian, Kabir, thank you for comments. Changing qa_ack to +. There is no description and BZ title implied that it would be QA task.
This was actually done for 6.2 and could be closed, but since it's an internal testing task and we need to do the same for 6.3, let's just keep the same issue. :-)
6.3 PR https://github.com/jbossas/jboss-eap/pull/1233
Carlo, you need to put the the EAP 6.2.0 dist into the location pointed to by -Djboss.test.mixed.domain.dir.
Note that it still 'reworks' the jars, so that the top-level directory is 'jboss-eap-6.2.0', the zip name is also important, e.g:
$unzip -l old-as7-releases/jboss-eap-6.2.0.zip
Length Date Time Name
-------- ---- ---- ----
0 11-20-13 21:47 jboss-eap-6.2.0/
0 11-20-13 21:47 jboss-eap-6.2.0/.installation/
0 11-20-13 21:47 jboss-eap-6.2.0/appclient/
0 04-06-14 11:34 jboss-eap-6.2.0/appclient/configuration/
7607 11-20-13 21:47 jboss-eap-6.2.0/appclient/configuration/appclient.xml
--- SNIP ---
https://bugzilla.redhat.com/show_bug.cgi?id=1098065 makes this a bit more user friendly
Can we close this one?
Comment 6 still applies, just with different versions.
I'm indifferent between closing this and opening another vs just continuing on; whatever anyone prefers.
Traditionally we only add these in the next minor or major, so 7.0.0 has the test for 6.4.0, and 6.4.0 introduced the test for 6.3.0 and so on. As I understand it this is for 6.4.x testing against 6.4.0, but we should not be changing the management API in micros which makes this test pointless. However that is the basic rule, so if we have actually changed something for whatever reason we can add this test.
As an aside, the setup of this test is quite complex, with duplicated profiles in the domain.xml. Upstream (i.e. WF10/EAP 7) we have simplified it a lot with a 'DomainAdjuster' per version (e.g. https://github.com/wildfly/wildfly/blob/master/testsuite/mixed-domain/src/test/java/org/jboss/as/test/integration/domain/mixed/eap630/DomainAdjuster630.java). This now boots up the DC in admin only mode, adjusts the profile to something which can work, and then starts the DC normally and the legacy HC.
Okay then, Kabir is actually right that we probably don't need this for EAP 6.4.0. And because there will be no more minor releases of 6.x, I think this can be closed.