-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Plugin upload workflow: Add 300s timeout to svn commit command #55621
Conversation
Looking at #55295 (comment), the recent svn commit commands all took up over 5 minutes (one of them even 10). I'm tempted to increase the timeout to 5 minutes to give a bit more leeway. |
I've increased the timeout to 5 minutes. I'd love to give this a shot for 16.9, which @justintadlock is going to release today. Anyone mind giving a quick rubber-stamp ✅ pls? 😊 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, based on my limited understanding of SVN and reading more about the http-timeout option here. I agree that it's worth trying this with the next release 😄
Thank you! Yeah, that's the docs I was perusing as well; I should've added a link!
🤞 |
Cherry-picked to the |
What?
Add a
60s300s timeout to the svn commit (and import) commands in the plugin upload workflow.Fixes #55295.
Why?
The Gutenberg release workflow that uploads the plugin to the WordPress.org plugin repositoty frequently experiences a timeout that results in the relevant tag not being created (see here for a list of recent failures), requiring to be created manually instead.
How?
Some investigation seems to have revealed that this timeout might be due to some post-commit hooks running on the server side. To remediate this, this PR adds the
http-timeout
option to give the svn command more time.Testing Instructions
Hard to test in isolation; I'd suggest we give it a try for the next GB release.