Closed danopia closed 1 year ago
I'm closing this issue for now, as our team won't have the capacity to work on this. But feel free to open a PR with this issue tagged.
I agree @danopia! Too bad, CircleCI isn't willing to address this.
What is the point of even having finish
if there is no when step to control its behavior? continue
has this, so it seems like an oversight.
The work around I am using generates a config, that just echos "Nothing to do here", but it is a waste of resources to spin up a whole container just so you can "do nothing".
Describe Request:
I am generating a new CircleCI configuration file to give to this orb:
Unfortunately, sometimes there are simply no workflows that I'd want to continue into. For example, a PR that only updates README.md will not match any entries in my mapping for
path-filtering-orb
. In this case CircleCI considers the continued build an error because there is nothing to do:In this case the documentation says to close out:
These are two different steps - I'm not aware of how to conditionally call steps based on the output of a previous step!
It seems as though this orb should have a third command that can dynamically switch between 'continue' or 'finish' depending on a parameter.
Examples:
Something like this could probably work, if nothing else:
I could also imagine there being a special check on the config on disk, for example if
.circleci/continue_config.yml
is empty (zero bytes) then finish instead of continuing.Supporting Documentation Links: