I know you can restart an entire workflow, but sometimes in a release process only one job in the workflow fails due to some third party system being unstable. I was wondering if there were any thoughts to allowing restarting a workflow from the job where it failed and also potentially restarting only one job in a particular workflow?
This would be really helpful. We won’t want to rerun all CI tests if only 1 job failed, we want rerun from where it’s failed.
Agreed. We have one workflow that has 9 jobs and it’s a pain to rerun the entire workflow if a single job fails.
Do we have any update on this thread?
I think this woudl be a very useful feature to avoid rerunning unnecessary time consuming jobs which are previously successful.
Another idea as workaround is to deouple the jobs into separate workflows (so the jobs can run more independently on the workflow level).
I’d love to see this feature as well. We moved over to Gh-Actions from CircleCI and this is the one feature we really miss.
I see build tasks failing intermittently in one of my projects, hence breaking the flow. I really miss this feature right now, definitely a flaw not to have it.
Did we have a plan about this? I want to track this process.
I also need this. I have macOS jobs that fail for no known reason. My guess is that they timeout waiting for capacity, but I don’t know. I would like to re-run only the failed job(s) in this case.
+1 specially for macos ios CI flows that sometimes need to re-run due to appstore timeouts and whatnot…
Yep, macOS fails randomly in
brew install mysql or other stuff, and having to wait 20 minutes (windows client + server) instead of ~5 mins (mac server) is painful