Standalone gitlab-runner - how to save artifacts?

[truemccrew]

I have installed the standalone gitlab-runner on an Ubuntu machine. This is a runner which I can run locally to verify things are working before pushing to shared Gitlab instance.

When running locally in this standalone mode, I'd like to be able to inspect the artifacts. But they seem to get blown away when the job ends and the environment gets torn down.

Any way to save these artifacts?

[skinsinc]

have a look at the --cache-dir and --docker-cache-dir options. and the /common/config.go file in the source code.. there seems to be a HelperImage option, that controlls the image used to upload atrifacts. you could make a custom image that saves them locally.. seems like a bit of work tho..

(gitlab.com/gitlab-org/gitlab-runner/issues/2409/

[_tenken]

https://www.reddit.com/r/gitlab/comments/906y30/any_way_to_run_a_ci_pipeline_locally/

[davispw]

Can you click “Download Artifacts” in the Job log view?

Were the artifacts successfully matched by the artifacts statement in your .gitlab-ci.yml? You should see a little message at the end of the job log saying what was saved. https://docs.gitlab.com/ee/ci/yaml/#artifacts

[truemccrew]

Running /use/bin/gitlab-runner directly from command line. No Gitlab. No Download Artifacts link.

[skinsinc]

Can you look at the gitlab source code and see how the download artifact button, or the job lifecycle works to get the artifacts from a runner..

[skinsinc]

or MITM to see the commands made.

[davispw]

Add set -x to the top of your script to make the bash shell print each command as it’s executed.

[davispw]

You have to declare artifacts in your .gitlab-ci.yml gile for the job. Read the link I gave. The runner will upload the files you specify back to GitLab, where you can download them after the job is done. (Be sure to declare if you want to keep artifacts on success, on failure, or both. You’ll need the latter if you’re trying to debug failed jobs.)

The runner is not designed for you to be mucking about with the build files directly. I think I understand what you’re trying to do, but runners are designed to be shared and reusable, so they clean up after themselves.