当 jenkins 作业在从机上运行时，如何使用 Jenkinsfile 管道脚本从主机读取 yaml 文件？

Question

I am building a Shared Library(I'm not a CI engineer) for Jenkins pipeline. As a part of it, we are thinking of giving configurations in yaml file and have Jenkinsfile pipeline script read from the yaml file.

So, we are planning to commit Jenkinsfile and yaml file in one git repository (let's say repo A) and the job is going to run on a slave machine utilising another git repository (let's say repo B). The Jenkinsfile will be executed from master after it clones repo A. The yaml file is also in master workspace. In the slave, repo B will be cloned and a build will take place as defined in the Jenkinsfile. But the question I have is, how do I read yaml file from Jenkinsfile script without having to clone repo A in slave ie, how I reference a file present in master and not in slave from Jenkinsfile? This question arises because, whatever file I am trying to open is being opened from slave and not from master.

Thanks in advance.

EDIT: Soemthing I forgot to mention. We actually thought of using stash from master and unstash in slave. But the problem is that we do only the job configurations and the environment is provided to us by some other team which also provides to many other teams. Because of that, master rarely has executors free. So, even when we run the job, it hangs waiting for the master to be free. Is there any other way to load the yaml file when the pipeline script is being loaded in master's memory?

Answer 1

I think the most straightforward way is to use the stash . Stashes are temporary packages that can be created on one node and copied to any other node.

There is some overhead on master for the package creation so stashes are not recommended for really big files, but they are ideally suited for your usecase of transfering a small configuration file.

node('master') {
    // Create temporary stash package on master
    stash name: 'MyConfiguration', includes: 'SomeFile.yaml'
}

node('MySlave') {
    // Copy to and extract the stash package on slave
    unstash 'MyConfiguration'
}

This expects 'SomeFile.yaml' to be in the workspace on master and will also extract it to workspace on slave. In case you want a sub directory of WORKSPACE , simply wrap the stash and/or unstash steps in a dir step.