-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to re-trigger a build from the build page #6524
Comments
The link gives 404 now because we delete all builds when the PR is merged/closed :D |
I think we can show a |
Hello. I was looking for this feature as well. FWIW, I think allowing trigger for both failing and successful builds is useful. This is because sometimes as a maintainer, I want to know if new upstream release on PyPI would break an already successful PR build. Also would be nice to have a "wipe cache" option. Currently some builds are failing due to invalid cache for pip 20.0. A wipe is necessary before rebuild. |
This is really useful for the PR builder. I think we need to figure out a good way to ship this 👍 |
This is most useful for PR builds, but I've enabled it for all builds currently. It might make sense to only enable it for PR builds, or other builds where we care about rebuilding a specific commit. Fixes #6524
This is most useful for PR builds, but I've enabled it for all builds currently. It might make sense to only enable it for PR builds, or other builds where we care about rebuilding a specific commit. Fixes #6524
+1 on the feature. We are hit by this problem when the build crashes (e.g. |
This is mainly for builds from a pull request (maybe would be good to add this to normal builds too?), sometimes the build fails for reasons that aren't related to the PR like https://readthedocs.org/projects/docs/builds/10259706/.
The status of the PR would be marked with the red X because of that. Travis and other services allow you to trigger a new build to refresh the status.
Currently, the only way to trigger a new build is by making another commit.
We could allow to re-trigger a build only on unsuccessful builds or maybe in all builds.
The text was updated successfully, but these errors were encountered: