Presently, if a change is made to an instance in the Manage Jenkins -> Configure System screen, those changes will not propagate to the SCM configuration of a project, which will continue to use the previous configuration.

Steps to replicate:

• Navigate to Manage Jenkins -> Configure System and create a Bitbucket Server instance
• Create a new Freestyle Project, and under SCM add the previously configured Bitbucket Server instance
• Return to the Manage Jenkins -> Configure System screen and change the URL
• In the Freestyle Project, schedule a build

Expected

The build will attempt to clone from the currently configured URL

Actual

The build will attempt to clone from the previously configured URL

Workaround

This issue can be resolved by navigating to the Project -> Configure, and clicking "Apply". The latest configuration will then be added to the SCM and cloning will work as normal.