Yeah, as @glenjamin said a support ticket is usually the most reliable way to get a response. I was on vacation all last week! 🙂
Thanks @conormcd! I think Marc might have spoiled us over the years! simple_smile
Is there a good way to cancel a job successfully if a dependent job was "halted" successfully?
I only can find instructions on how to cancel a single step
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 @borkdude, 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?
Dynamic config was what I was about to suggest.
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.
For any given workflow right now it is a DAG of jobs and we unblock jobs strictly on the success of preceding jobs.
makes sense, i can go ahead with this if its the recommended way. thanks!