It would be really helpful if artifacts could be supported
:+1: for supporting artifacts. Or at the very least it could be helpful to produce an explicit warning/error when these actions are used. AFAICT, a step using the artifact actions will succeed but no artifact will be uploaded/downloaded.
Great call, good feature to add. Anyone have a sample workflow to use?
This is use case we have in buildpacks/pack. We ultimately want to run test and build always and then use the artifacts for the release job.
The source can be found here:
Upload:
https://github.com/buildpacks/pack/blob/c9745af053eabf812bf2fdab1695488a01022093/.github/workflows/build.yml#L77-L81
Download:
https://github.com/buildpacks/pack/blob/c9745af053eabf812bf2fdab1695488a01022093/.github/workflows/build.yml#L92-L104
Issue is stale and will be closed in 7 days unless there is new activity
Is there any progress? Can I help with something?
Typically these artifacts are shipped via the gh API and then referenced by url.
I don't know how other parts, if any, work with mocking or intercepting GH API calls but I would think that is necessary to properly mock this locally. Am I wrong?
How works actions/cache? Seems similar no?
we also have the same issue while using upload-artifacts, we got the error
[CI/build] 💬 ::debug::Root artifact directory is /github/workspace/build
[CI/build] ❗ ::error::Unable to get ACTIONS_RUNTIME_TOKEN env variable
[CI/build] ❌ Failure - Upload
it would be great if it can be mocked.
Issue is stale and will be closed in 7 days unless there is new activity
Seems like this should have remained open. It's a pretty big blocker for full use.
Artifacts is one of those key actions that many workflows use, and bc of that its a blocker for local dev working... Having this along with cache support would make act the tool we all need to fully develop workflows locally, instead of running workflows to try things and waiting a lot of time
Most helpful comment
Seems like this should have remained open. It's a pretty big blocker for full use.