Hi,
I’m running using the drone/drone:0.5 image (updated as of today) using the mysql driver and connecting to an enterprise github instance. When I try to increase the timeout for a particular repo it gives me a success message but when I reload the page it shows the original 60 minute timeout. Enabling debug (DRONE_DEBUG=true) shows the http PATCH request being made and returning 200 status but I’ve verified in the mysql table it still has the 60 minute value. Any ideas?
I should note updating the other repo settings (deploy hook, tag hook) seems to work fine.
Bryan
I’m running using the drone/drone:0.5 image (updated as of today)
awesome!
When I try to increase the timeout for a particular repo it gives me a success message but when I reload the page it shows the original 60 minute timeout
only an admin can update the timeout. Check out this guide for setting up admin users http://readme.drone.io/admin/user-admins/
previously drone managed admin users in the UI and the first user to create an account was the admin by default. This caused some confusion. There was also a desire to make this more reproducible for teams laucnhing drone with chef / puppet / ansible / etc. So in 0.5 I experimented with using environment variables to explicitly set admins. This of course seems to have caused more problems than it solved 
and is something we’ll look at improving in future releases.
Yes you are correct. I was configured to be an admin but github has my username capitalized. After fixing that I was able to change the timeout. Thanks for the help