For the past couple of weeks it seems like my builds don’t have a rebuild option anymore, but only prompt me to rebuild with SSH. This happens for both failed and succeeded builds. I was trying to debug some flaky specs and needed to retry succeeded builds but couldn’t find an option to do so neither on the build page nor on the repo index since it only appears for failed ones. I ended up resolving it by using rerun on the workflow rather than just the tests but it’s obviously not ideal. Let me know if there’s some setting I need to change to get the old behavior back.
We have plans to add “Rerun Workflow” button on the jobs (build) page. For now, you would have to navigate to the “Workflows” page to rerun a Workflow or rerun a Workflow from failed jobs.
9 months later. This is such poor design. How often do I have to re-run the failing build? Like 50% of the time. 5 clicks for what should be one click. Boo.
This is a pain point for our company as well. Apart from the awkward additional clicking around, it’s problematic because you cannot rerun failed before all the tasks are done. So if task A in a workflow fails and task B is still running, you have to wait for task B to fail/succeed before you can rerun failed tasks. This can severely slow people down.
I’ve not tried it, but has anyone looked at making rebuild requests using the API? I imagine POST: /project/:vcs-type/:username/:project/:build_num/retry might be a good place to start (API reference).
I appreciate that folks on this thread would prefer a solution integrated into the CircleCI UI, but if it gets people productive again, a quick console solution might suffice.
