Uploading artifact on failure

[evertonlperes]

Hi there,
I was wondering to ask if there's a way to upload an artifact (zip) when the previous step has failed.
On Cirrus CI looks like the artifact will only be uploaded with the previous step has passed.

Is there a way to include something like:

build_and_test_task:
  binaries_artifacts:
   on_failure: true
   path: "screenshots/*"
   format: zip

Just looking for some opportunities to upload some screenshots results from the cirrus runner.

Thanks!

[fkorotkov]

Hey @evertonlperes, you can do it already with execution behaviour feature. Just wrap your artifacts instruction in on_failure or even always:

on_failure:
  binaries_artifacts:
     path: "screenshots/*"
     format: zip

[evertonlperes]

Sure thing. Here we go: https://cirrus-ci.com/task/5550026899324928?logs=test#L48

[fkorotkov]

I think this might be the typo(you need to use an absolute path): https://github.com/evertonlperes/rancher-desktop/pull/10/files#r766653211

[evertonlperes]

That's weird, even with the absolute path, still getting the same behaviour though:
Uploading 0 artifacts for /tmp/cirrus-ci-build/home/ranchertest/pw-log.txt

And the file wasn't uploaded even though the file exists:

root@cirrus-task-4661075479101440:/tmp/cirrus-ci-build# ls -la /home/ranchertest/pw-log.txt -rw-rw-r-- 1 ranchertest ranchertest 32850169 Dec 10 16:41 /home/ranchertest/pw-log.txt

https://cirrus-ci.com/task/5934862317125632

[fkorotkov]

My bad. I just realized and it's actually stated in the docs:

Right now only storing files under $CIRRUS_WORKING_DIR folder as artifacts is supported

So you'll have to copy over the file into your working directory and then upload it. It's required for now to figure out relative paths in the resulting archive. I've created cirruslabs/cirrus-ci-agent#197 to support uploading artifacts by arbitrary path.

[evertonlperes]

Ough, I just misunderstood the sentence, my bad either.
I thought any file under $CIRRUS_WORKING_DIR/* will be uploaded... :P
I'll create a workaround just to get it working on my stuff and wait to the fix being release.

Glad that you catch it. Thanks for helping and opening the fix.

[evertonlperes]

Closing this by: cirruslabs/cirrus-ci-agent#197

[evertonlperes]

It did the trick moving the artifacts around:

  always: # or on_failure:
    custom_script: |
      cp -R /home/ranchertest/e2e/reports/ .
    logs_artifacts:
      path: "/reports/*"

On my scenario, I need to run the E2E tests as a non-root user due our project requirements. That's the reason to move the files created as a non-root to a root environment in order to be uploaded.