Our Bitbucket server frequently takes >10s to handle requests (and it's unlikely that we can improve the performance of this); this causes a few issues:

• On a newly seeded (jobdsl) project this can leave checkout failing as the internally configured gitScm is not configured correctly (workaround seems to be to save it again) - it would seem to also be worth adding a check based on the state to the point where this is initialized
• Status reporting frequently times out - this is the biggest issue as stuck builds block merges
• Seems to cause issues on library caching (empty library is cached)
• Seems to cause issues on lightweight checkout of script

I'd propose adding another system property to facilitate setting the default (10s) timeout that okhttp defines - maybe later this could be added to the Bitbucket server configuration page.