Why do I encounter a "source path does not exist" error from the Gitlab Runner Docker executor when downloading jobs in Simulink Check R2025b?

I am following the workflow in "Process Integration and Artifact Management for GitLab" to generate a GitLab pipeline. The pipeline structure is as follows:

• The top-level ".gitlab-ci.yml" triggers a downstream (child) pipeline generated by Simulink.
• This child pipeline runs a series of jobs for model analysis and testing, including:
  • padv.builtin.task.MergeTestResults
  • padv.builtin.task.RunTestsPerTestCase
  • padv.builtin.task.RunModelStandards

In the logs for all three jobs, I notice that the executor errors with a "source path does not exist" message while running "job_download.py":

python3 "$MW_PIPELINE_UTIL_PATH/py/job_download.py" --jobname "$CI_JOB_NAME"...                               JOB DOWNLOAD...Downloading artifacts to _downloads_ folderSource path does not exist: ./<path name>

Why am I getting this error?

Answer 1

[MathWorks Support Team]

This can occur due to a configuration issue in the MATLAB script you are using for pipeline generation. In particular, please check how you have defined your "padv.pipeline.GitLabOptions" object.

As per the "padv.pipeline.GitLabOptions" documentation, the "NetworkStoragePath" property must be set to a shared network location accessible by all agents running the pipeline. If this property is set to something like "./", this will prevent artifact propagation between pipeline jobs.

Note that for containerized environments, a shared path can be achieved by mounting a shared volume to all runner containers using the

"runners.docker" configuration section

.

Alternatively, you can use other artifact storage options such as JFrog Artifactory, Amazon S3, or Azure Blob Storage.