Hello,
How can I restart a failed build on Azure? https://dev.azure.com/Python/cpython/_build/results?buildId=43161&view=logs&j=18d1a34d-6940-5fc1-f55b-405e2fba32b1
Regards
Antoine.
On Tue, 21 May 2019 at 19:10, Antoine Pitrou <antoine@python.org> wrote:
Hello,
How can I restart a failed build on Azure? https://dev.azure.com/Python/cpython/_build/results?buildId=43161&view=logs&j=18d1a34d-6940-5fc1-f55b-405e2fba32b1
You can close and reopen the PR, but that restarts every build. I think there should be a way to restart an individual build, but it requires certain rights. I just checked, and I don't have the right to do so, and I'm afraid I don't know who gives out those rights (or even if it's something that we do give out to individual core devs).
Paul
Le 21/05/2019 à 20:28, Paul Moore a écrit :
On Tue, 21 May 2019 at 19:10, Antoine Pitrou <antoine@python.org> wrote:
Hello,
How can I restart a failed build on Azure? https://dev.azure.com/Python/cpython/_build/results?buildId=43161&view=logs&j=18d1a34d-6940-5fc1-f55b-405e2fba32b1
You can close and reopen the PR, but that restarts every build.
I tried to do that... but stupid Miss Islington deleted the branch :-/
There's a link that does that on _github_. (On mobile, sorry for terseness).
Alex
On Tue, May 21, 2019, 2:10 PM Antoine Pitrou <antoine@python.org> wrote:
Hello,
How can I restart a failed build on Azure?
Regards
Antoine.
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Close/reopen is still the easiest way, unfortunately. I've been bugging the team to improve this, but other priorities have been higher.
And I see this is a backport, which means as soon as you close it miss-islington will delete the branch and there's no way to restart it.
If we integrated Pipelines through the GitHub app then it would have a "re-run check" button. I haven't done that yet as I don't have permissions to update our GitHub org and haven't forced someone who does to sit down and do it with me :)
For those of us who can log in (GitHub auth integration is also delayed, so it's manual user management right now) there should be a "Rebuild" button in the new UI, but that's missing on your build for some reason. I'll ping some people to find out.
Cheers, STeve
On 21May2019 1110, Antoine Pitrou wrote:
Hello,
How can I restart a failed build on Azure? https://dev.azure.com/Python/cpython/_build/results?buildId=43161&view=logs&j=18d1a34d-6940-5fc1-f55b-405e2fba32b1
Regards
Antoine.
Maybe worth implementing a retest command so our bots can retrigger the
tests without closing PR.
Jenkins has this command.
ᐧ
On Tue, May 21, 2019 at 8:40 PM Steve Dower <steve.dower@python.org> wrote:
Close/reopen is still the easiest way, unfortunately. I've been bugging the team to improve this, but other priorities have been higher.
And I see this is a backport, which means as soon as you close it miss-islington will delete the branch and there's no way to restart it.
If we integrated Pipelines through the GitHub app then it would have a "re-run check" button. I haven't done that yet as I don't have permissions to update our GitHub org and haven't forced someone who does to sit down and do it with me :)
For those of us who can log in (GitHub auth integration is also delayed, so it's manual user management right now) there should be a "Rebuild" button in the new UI, but that's missing on your build for some reason. I'll ping some people to find out.
Cheers, STeve
On 21May2019 1110, Antoine Pitrou wrote:
Hello,
How can I restart a failed build on Azure?
Regards
Antoine.
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
On 21May2019 1234, Mariatta wrote:
Maybe worth implementing a
retestcommand so our bots can retrigger the tests without closing PR. Jenkins has this command.
Or at the very least, a command so the bot can close/reopen the PR itself without deleting the branch.
I honestly don't think we'll ever truly get to 100% reliability across all CI systems, or every check getting to the point where they're fully integrated with GitHub and have their own "rerun" button, so I suspect we'll be closing and reopening PRs for a while to come.
Cheers, Steve
participants (6)
-
Alex Gaynor -
Antoine Pitrou -
Cheryl Sabella -
Mariatta -
Paul Moore -
Steve Dower