GitHub Community
How to retry a build that failed? #26037
-
|
I had a build fail for a reason unrelated to my code (in the setup-node action - possible a network issue or something, it’s not clear). I can’t rind any way to retry this build without pushing another commit (which means all the other parallel tasks like running on other OSes will be repeated). |
Beta Was this translation helpful? Give feedback.
Replies: 13 comments 2 replies
-
|
Hello! We currently don’t have the retry button enabled for Actions. 100% agree this is super important. We’re working on it now, won’t be much longer. 😀 |
Beta Was this translation helpful? Give feedback.
-
|
This does seem to be there now. However, I’m seeing that I get a “check rerequested” event is in the |
Beta Was this translation helpful? Give feedback.
-
|
👍 thanks! We’re working on it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Retry is hugely important to us :slight_smile: The ability to retry individual tasks/checks as well :) |
Beta Was this translation helpful? Give feedback.
-
|
For future runs this should now be solved https://github.blog/changelog/2019-09-30-github-actions-deterministic-re-runs-for-workflows/ |
Beta Was this translation helpful? Give feedback.
-
|
I don’t understand how re-runs work. When I have a failed task, there’s an info icon next to it with a tooltip that says “This check suite has disabled re-running individual check runs”. Is there something I need to do to enable this? |
Beta Was this translation helpful? Give feedback.
-
|
Will we be able to retry specific jobs rather than the entire workflow? Right now I only see the option to Re-run all checks. If I am running multiple jobs in parallel and only one fails I would like the ability to rerun just that one job. |
Beta Was this translation helpful? Give feedback.
-
|
I cant find it and it’s now 6 months since your message, am I missing it or is Github still working on it? |
Beta Was this translation helpful? Give feedback.
-
|
We don’t see a re-run command sometimes. https://github.com/submariner-io/shipyard/runs/666918597?check_suite_focus=true I remember seeing it in the past. It would be nice to be able to re-run specific tests. |
Beta Was this translation helpful? Give feedback.
-
|
Although the possibility to rerun failed workflows is great, it would be super great if there’s an option to run only the failed jobs. Is this already there and I’m missing it? Is there a plan to implement it? |
Beta Was this translation helpful? Give feedback.
-
|
Updating this, as my old comment is very out of date at this point. Re-running an entire workflow is possible via the re-run button on the top right or the Actions API. The re-run button will trigger the entire workflow to run again. In the future, we’ll be making this more specific and allowing for individual jobs within a workflow to be re-run. |
Beta Was this translation helpful? Give feedback.
-
|
mscoutermarsh:
If you like me think that “Hey this is not true, there is no re-run button!” it’s likely that your job is not finished yet and that “re-run” button is actually a “cancel” button. So you just need to cancel your job before you can re-run it. |
Beta Was this translation helpful? Give feedback.
-
|
We have checks that run via webhooks. The Actions API is not enabled, so we don't have a retry button. We can re-run webhooks, but the webhooks interface only shows the 17 most "Recent Deliveries", so I can't actually re-deliver anything older. The use case here is when code from one PR fixes a build issue with many other PRs. When the fixing PR is merged, the rest of the PRs need to be rebased with the new merged base branch. It's not always feasible to push an empty commit to every PR because they are usually all branches sitting on various developers' forks. |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, the great thing would be for PRs to rebase to the base branch's new HEAD automagically whenever a pull request is merged. |
Beta Was this translation helpful? Give feedback.
-
|
Something like that needs human interaction as otherwise conflict messes are likely to accumulate. A request for a robot to do it sounds fine, but automagic means that if you're landing a series of PRs, you have to wait for pipelines to refresh after each merge (wasting a lot of CI resources as even further PRs are going to spin CI for each PR that lands ahead of it). |
Beta Was this translation helpful? Give feedback.
Updating this, as my old comment is very out of date at this point.
Re-running an entire workflow is possible via the re-run button on the top right or the Actions API. The re-run button will trigger the entire workflow to run again.
In the future, we’ll be making this more specific and allowing for individual jobs within a workflow to be re-run.