Resolution
In newer version of Jenkins the runs were stored as a timestamp value. Starting with 1.597 the runs are now stored as numbers instead. There is a *one time startup *performance issue when upgrading as this conversion needs to happen. In the Jenkins logs (usually in /var/log/jenkins), there are warnings which indicate the migration is happening. If this continues to happen, then please file a new support ticket.
For more information please go to the Jenkins wiki: 1.569+ Migration.
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.