-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update test-sverchok.yml #4141
Update test-sverchok.yml #4141
Conversation
@portnov i have movement. we probably don't want to hardcode something like ?
i don't know how to mix literals with strings. |
@zeffii
Shell:
The difference is, in shell you do not have any special "context markers" for f-strings (like so,
Shell
|
@portnov @vicdoval why is the newly downloaded blender/python dependancies gone when this job is triggered again? that caching is a little beyond my ability to figure out,.. unless ofcourse i start throwing all kinds of mad stuff at the actions until something clicks. but maybe someone knows. https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows i'll keep poking at it :) |
we make some kind of a key file using |
Maybe you should change cache key? For example, "empty" -> "b29" |
Hi! Portnov shared a link to this PR, so I took a peek. The main problem here is that the cache key doesn't depend on anything, it's a fixed value. So you're using the cache that you created some time ago, and GitHub doesn't update it because the key at the end of the run is the same as at the start of the run. You can fix this temporarily by changing the key as @portnov suggested, but you'll have to do it every time you change anything about Blender installation (e.g. Blender version or release). A better approach would be to include Blender version in the key, something like this: jobs:
build:
env:
blender_version: "2.93"
steps:
- uses: actions/cache@v2
with:
path: ./installation
key: blender-${{ env.blender_version }} Now every time you change The cache can even depend on the workflow file itself: Hope this helps. |
Ah, and you don't need to manually add a "post cache" step, GitHub updates the cache automatically at the end of each run (if the key changed). |
@Minoru that is very helpful! the syntax is new to me, but i'll have time tomorrow to complete this. if someone else doesn't do it already. |
i still have no idea what i'm doing. but this is progress. |
thank you for your time @Minoru ! works as hoped ! |
i'll keep poking around in this, and document it. |
testing yaml blindly. eat me.
ok a few notes then.. for the
bash
leppers such as myself :)basename from an archive
this is the equivalent to python