Hello all, I just have two questions (no issue that needs solving, just some unexpected Jenkins behavior).
I recently moved our Jenkins installation to a new server by installing the same version of Jenkins on the new server and copying configuration files and the plugins and jobs folders from our old server (don't ask). Jenkins is now working, however I experienced some unexpected things. I need to document the server migration and I'd love to be able to explain the following: - I updated each Job configuration to reference new server paths and URLs. Exceptions written to log and console contained the old configuration paths and URLs even after I updated them. Exception Stack Traces continued to reference old configuration until each Jenkins Job was successfully built on the new server for the first time. This was misleading because I repeatedly checked the new configuration wondering where these old references were coming from. *Where was Jenkins getting the old configuration from?* - The entire Jenkins Jobs folder was copied from one server to another. Even though each job folder contains an existing nextBuildNumber, they all reset back to one. I was not expecting that and was forced to set it manually. *Can anyone explain this?* Thanks
