[
https://jira.jboss.org/browse/JBWS-3049?page=com.atlassian.jira.plugin.sy...
]
Alessio Soldano commented on JBWS-3049:
---------------------------------------
I've moved all the hudson jobs to using a copy of clean AS build, so every job now
runs against a vanilla AS, which is what final users do most of the time.
For covering the usecase Richard mentioned above, I've added a stack switch job for
each container that basically runs all 6 combinations of stack changes and verifies the
obtained AS is equivalent to the one that can you can get directly installing a given
stack to the vanilla AS.
IOW:
vanilla_AS + CXF = VC
vanilla_AS + METRO = VM
vanilla_AS + NATIVE = VN
assert VC + NATIVE = VN
assert VC + METRO = VM
assert VM + NATIVE = VN
assert VM + CXF = VC
assert VN + METRO = VM
assert VN + CXF = VC
Hudson jobs need to test binary and src distros against vanilla JBoss
AS
------------------------------------------------------------------------
Key: JBWS-3049
URL:
https://jira.jboss.org/browse/JBWS-3049
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: productization
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-3.4.0, jbossws-metro-3.4.0, jbossws-native-3.4.0
.. to prevent issues like JBWS-3048.
I'm thinking about creating a zip of the jboss AS that is built by the AS-XYZ jobs
and unzipping it in the bin/src distro jobs. The content of the zip is then used, so that
we have a fresh install and not something already processed by the installations in the
core jobs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira