Feature: support cross-workflow job dependencies via API #75
Description
Description
Run-on sentence, but: I have a job in workflow A that builds a Helm chart that depends on Helm artifacts produced in workflow B. I want this orb to insert a boilerplate/template job in workflow A before my Helm chart build that polls the API and waits for the jobs in workflow B to complete before exiting with a successful status so the job in workflow A can run.
- The job name could be descriptive about what it is for and what it's waiting on.
- I'll have to think of a way to indicate this cross-workflow dependency.
The present work-around is to simply depend on the user to rerun the workflow starting from failed jobs once the jobs it depends on have completed.
Another idea is: what if we have complete workflows that are dependent on one another?
References
https://circleci.canny.io/cloud-feature-requests/p/cross-workflow-job-dependencies
https://gist.github.com/natemellendorf/7bbc92c427d1d5bd8db8512cff0f8e60