This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-07
Channels
- # announcements (2)
- # asami (2)
- # babashka (15)
- # babashka-sci-dev (31)
- # beginners (130)
- # boot (4)
- # cider (5)
- # circleci (12)
- # clj-kondo (10)
- # cljs-dev (8)
- # clojure (7)
- # clojure-czech (14)
- # clojure-europe (19)
- # clojure-france (5)
- # clojure-uk (2)
- # clojured (23)
- # clojurescript (11)
- # conjure (8)
- # datomic (5)
- # emacs (1)
- # etaoin (8)
- # events (2)
- # fulcro (10)
- # graalvm (18)
- # gratitude (1)
- # holy-lambda (16)
- # honeysql (4)
- # introduce-yourself (1)
- # jobs (2)
- # kaocha (3)
- # london-clojurians (1)
- # lsp (53)
- # off-topic (16)
- # other-languages (2)
- # pathom (4)
- # pedestal (3)
- # podcasts-discuss (1)
- # portal (10)
- # re-frame (69)
- # reitit (2)
- # shadow-cljs (11)
- # vim (7)
- # xtdb (29)
Yeah, as @glenjamin said a support ticket is usually the most reliable way to get a response. I was on vacation all last week! 🙂
Is there a good way to cancel a job successfully if a dependent job was "halted" successfully?
I'm not entirely clear on what you're trying to do. Would you mind giving a more complete example?
also coming in from the same question as @U04V15CAJ, we on the #babashka and other projects want to "short" the ci if the changes are irrelevant, like only .md
files changing. we have a script that does that and is called like this here: https://github.com/babashka/babashka/blob/master/.circleci/config.yml#L29
it turns out that command only stops that step and the things dependent on it still continues as usual. is there a way to stop it in a "cascaded way" without failing it?
is https://circleci.com/developer/orbs/orb/circleci/path-filtering and dynamic config the recommended way for having the ability to short the run on some logic?
You don't need to use that orb if it doesn't suit you though, you can use anything to generate the follow-on config.