Hi Torque devs, I am currently investigating the Jenkins build failures. The main reason is that running the torque-test from the root fails due to path issues, which are hidden at multiple places.
To supply a "workaround with the *-jenkins profiles in the torque-test module seem not enough anymore, this was IMO always kind of a hack. Nevertheless it is not obvious to me at the moment, how to let jobs in Jenkins share a single JOB_BASE_NAME or workspace root, although propagating environment variables from one build to the another seems to be possible. We might solve this only once we move to pipeline building with a JENKINSFILE, which we may do when migrating to GIT ... From a practical point of view, running torque-tests module locally on a developer machine seems to me at the moment more important. IMO either we remove entirely torque-tests as a root module or allow running the torque-test tests on the other side only from the parent root. Torque-Test is better remembered as being a suite of integration tests, we have to set a database to run it, by default now hsqldb (or before the retirement derby), which could be run a simple way without further system dependencies .. My suggestion is currently to completely remove the support for running the integration tests from the parent root. This change would simplify the code and configuration, but we have to change the documentation to a two -step release: Before preparing a release the torque-test integration test SHOULD be done, at least for one database, separately to check for general integration failures . What do you think? We should at least declare derby database as not supported anymore for the upcoming release, and flag the two jenkin profiles as broken at the moment. With best regards, Georg
