Ideally I think the qa / configuration should be organised like this: A first job builds the distribution and runs the tests (default in memory mode) while building the distribution. Let's call this the distribution job. Then the container matrix is a dependent job that only runs when the first job succeeded. The container matrix runs will start from the distribution that is build in the distribution job. The distribution is unzipped. In the distribution there is an ant script that can install jbpm into jboss as. That uses some property files that specify the connection settings. Then the qa overwrites those properties file with the specific properties of that job (similar to how we now do it with the profiles). And then the qa invokes the ant script that installs jbpm into the AS for that specific test run. That way, the properties files with the specific configurations for the qa lab database are also somewhere in the hudson directory, but not in the same format. And they would be used after the distribution is unpacked. It would also simplify a lot the comlexity of property resolution in our current build. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224904#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...