This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-29
Channels
- # adventofcode (8)
- # babashka (12)
- # beginners (91)
- # calva (6)
- # cider (2)
- # circleci (11)
- # clj-kondo (19)
- # clojure (202)
- # clojure-australia (7)
- # clojure-brasil (1)
- # clojure-europe (123)
- # clojure-nl (2)
- # clojure-poland (24)
- # clojure-uk (6)
- # clojured (1)
- # clojurescript (91)
- # core-async (23)
- # cursive (16)
- # data-science (5)
- # datomic (26)
- # emacs (27)
- # events (2)
- # graalvm-mobile (50)
- # graphql (4)
- # honeysql (4)
- # instaparse (33)
- # lsp (24)
- # meander (22)
- # nrepl (3)
- # off-topic (26)
- # pedestal (1)
- # re-frame (15)
- # releases (1)
- # sci (1)
- # shadow-cljs (20)
- # tools-deps (22)
I think I ran into a use case for which there's no syntax
I want a restore_cache
cache key that will last 24h. Rationale being, I don't want to spam an API provider with one request per build. But a permament cache wouldn't be useful either since the API's results can change over time.
This is the section that describes the possible syntaxes:
yes, that's what I'm seeking but circle's syntax seemingly doesn't allow to embed the output of an arbitrary command there
a few things could work for me:
* ability to use the output of arbitrary commands
* allow vanilla env vars, not from contexts
* add something akin to epoch
, just not so fine-grained
The easiest way around that is to echo the output into a file and then use the checksum of that file.
I gave it a think and it doesn't sound like it would work for my use case. I need to cache an internal cache dir (this API uses such a cache locally), not a result set. The API itself must be called in every run; caching results would be incorrect In any case I'd really appreciate the declarativeness of saying "dir foo should be cached for 1 day"