Downloading an Artifact that Does not Exist Yet #27041
-
I have what I feel is a fairly simple situation where I would like to cache my Python dependencies within my
In a nutshell, I want to download the I’ll eventually be splitting this up into its own job, maybe I’ll call it When I run
It seems rather arbitrary to have to run my workflow once with I am new to GitHub actions: what is the design pattern for doing this? I feel like I’m trying to do something fairly simple but running into a roadblock, and there’s no How do I try to restore an artifact and ignore errors if it does not already exist? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Technically you can cheat and use:
to force your later steps to run. This way your first run might technically “fail”, but it will “prime” your fake cache for the second run. Formally, github clearly wants you to use |
Beta Was this translation helpful? Give feedback.
-
jsoref:
Yes, this is the idea and was the solution. I was confused as to how Solution:
|
Beta Was this translation helpful? Give feedback.
-
Formally you want the cache early:
actions/cache/blob/0638051e9af2c23d10bb70fa9beffcad6cff9ce3/action.yml#L22-L24 Specifically, it relies on
actions/cache/blob/0638051e9af2c23d10bb70fa9beffcad6cff9ce3/examples.md#python---pip
|
Beta Was this translation helpful? Give feedback.
Technically you can cheat and use:
to force your later steps to run. This way your first run might technically “fail”, but it will “prime” your fake cache for the second run.
Formally, github clearly wants you to use
actions/cache
instead.