Closed Anirban166 closed 8 months ago
After some reading, I saw that the latest version of upload-artifact
(v4) allows for artifacts to be identifiable within a workflow (after their generation and uploading of course, with a reference to that step).
Given that the action's API can now create an artifact ID that is available within the succeeding steps of the workflow, I can use it to construct the URL to that specific artifact for one to download directly.
Here are the release notes, and to quote from that release in December last year:
Artifacts will be scoped to a job rather than a workflow. This allows the artifact to become immediately available to download from the API after being uploaded, which was not possible before.
I'll be using this thread to document and discuss the part of using
upload-artifact
to create downloadable artifacts, the contents of which consist of thedata.table/inst/atime/
folder as generated after a successful run ofatime::atime_pkg
within my workflow.I initially tested the step with
compression-level
set to 9 (highest forZlib
as can be specified forupload-artifact
) in case artifact sizes were large (was a known issue withatime
and @DorisAmoakohene encountered that earlier while using Siyao's action), but it seems the default works well too now (artifact size was in kilobytes for two small test cases put undertest.list
).