Currently, I am utilizing the self-managed version 14.6 of GitLab. In my .gitlab-ci.yaml pipeline file, I have defined two jobs: build and deploy. The build job runs on a docker executor through gitlab-runner and generates an artifact named build/, which contains nodejs codes and is stored in the working directory of the gitlab-runner server. My intention is to utilize this artifact in the subsequent job where an ssh executor is used to serve web content - essentially, the ssh-executor represents a remote nginx server. Unfortunately, when executing the command cp build/ /to/ssh/executor/path, I encounter the following error message:
cp: cannot stat ‘src/build’: No such file or directoryBelow are the configurations from my pipeline yaml:
build react job:
stage: build
script:
- npm install
- npm run build --scripts-prepend-node-path=auto
artifacts:
paths:
- build/
untracked: true
deploy on production:
stage: deploy
tags:
- my-srv # this refers to the ssh-executor runner
rules:
- if: ($CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH || $CI_COMMIT_BRANCH == "develope")
script:
- cp -r build /path/on/my/server/web/content
- docker-compose up -d
needs:
- job: build react job
artifacts: true
In an attempt to establish a relationship between the deploy stage and the build stage, I have experimented with the dependencies: and needs sections, but unfortunately, none of these approaches yielded the desired results. Shown below are the configurations for the my-srv runner found in /etc/gitlab-runner/config.toml:
[[runners]]
name = "my-srv"
url = "http://gitlab.example.com/"
token = "s8XljhkxJd-qj7WxCcew"
executor = "ssh"
[runners.custom_build_dir]
[runners.cache]
[runners.cache.s3]
[runners.cache.gcs]
[runners.cache.azure]
[runners.ssh]
user = "user"
password = "pass"
host = "172.20.ip.addr"
port = "22"
identity_file = "/home/gitlab-runner/.ssh/id_rsa"
Any insights or suggestions would be greatly appreciated.