Subsequent build job in Jenkins does not find workspace file

Question

I have separated my build tasks in several jobs. The following is a simplified structure.

The basic jobs are:

• compile
• quick-tests
• full-tests-part-1
• full-tests-part-2

Additional jobs are:

• full-tests
• full-build

Each job is configured to accept a workspace parameter to allow all jobs to be executed on the same code (workspace). This is passed from any calling job. Besides, all jobs are running on a slave node.

Job full-tests is configured to bundle the "full tests". Therefore it uses the build step Trigger/call builds on other projects with projects full-tests-part-1, full-tests-part-2.

Job full-build is configured to bundle the build pipeline. Therefore it uses the build step Trigger/call builds on other projects with projects compile, full-tests.

Job compile checks out the Git repository and compiles the code. Afterwards it starts the quick tests. Therfore it uses the post build action Trigger parametrized build on other projects with project quick-tests.

All compilation and test runs are triggered by Ant scripts.

When I trigger the full-build job, the following job sequence results:

    full-build
        compile (triggers quick-tests)
        full-tests
            full-tests-part-1
            full-tests-part-2
    quick-tests

The problem is, that the "full tests" are failing, whereas compile and quick-tests succeed. Both, the full and the quick tests, use the same build.xml in the same workspace, but the "full tests" complains.

Quick tests:

    Buildfile: J:\jenkins-slave\workspace\full-build\272\project-path\build.xml

Full tests:

    ERROR: Unable to find build script at J:\jenkins-slave\workspace\full-build\272\project-path\build.xml

Does anyone know whether there is a difference in "seeing" the workspace files depending on whether the job is part of the build (triggered as build step) or not (triggered as post build action).

If anything is unclear, please let me know.