|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
In our normal (and sadly complex) build jobs we invoke ant twice. First ant complies and builds the database tools, then the database tools are used to build the test database, then ant is used to run all the tests. The configuration options are added to the second / last ant invocation while they are required in the build step (first invocation).
There is an additional problem in that the library location is slave specific while the job can run on multiple slaves (above the e:/Jenkins/workspace requires that all slaves be run from e:/Jenkins/ which is not the case for our slaves).
Our workaround is to use %WORKSPACE% relative references on the first invocation.
I would recommend that all ant invocations get relative references, e.g. %WORKSPACE%/../../caches/artifactory-plugin/2.2.7