You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think for the cache key we can just use the serialized / rendered cache output to JSON to capture all Jinja variables. We should also find what variants are applied to dependencies and lastly, the build / target-platform should influence the cache key.
Currently, "used variables" from Jinja are ignored in the cache section.
Also, the script section might contain "lazily" evaluated Jinja variables.
The text was updated successfully, but these errors were encountered:
I think for the cache key we can just use the serialized / rendered cache output to JSON to capture all Jinja variables. We should also find what variants are applied to dependencies and lastly, the build / target-platform should influence the cache key.
Currently, "used variables" from Jinja are ignored in the cache section.
Also, the script section might contain "lazily" evaluated Jinja variables.
The text was updated successfully, but these errors were encountered: