Checks all the upstream sources for any versions of the core Jenkins distribution that are not installed in the update center. If any versions are found, they will be queued for download.

If Core is set to track the Latest version and one of the downloaded versions is newer than the current latest version, then this will result in the newer version being immediately published once the download has been completed. (See the section called “Version number rules” for a description of how version numbers are compared by Jenkins.)

If Core is set to either None or a specific version, then no change to the published version will take place.

Checks all the upstream sources for any versions of each plugin with at least one version currently installed in the update center. If any versions are found, they will be queued for download.

If any of the plugins are set to set to track the Latest version and one of the downloaded versions is newer than the current latest version, then this will result in the newer version being immediately published once the download has been completed. (See the section called “Version number rules” for a description of how version numbers are compared by Jenkins.)

If a plugin is set to either None or a specific version, then no change to the published version will take place.

Checks all the upstream sources for any versions of the core Jenkins distribution that are not installed in the update center. If any versions are found, they will be queued for download.

If Core is set to track the Latest version and one of the downloaded versions is newer than the current latest version, then this will result in the newer version being immediately published once the download has been completed. (See the section called “Version number rules” for a description of how version numbers are compared by Jenkins.)

If Core is set to either None or a specific version, then no change to the published version will take place.

Checks all the upstream sources for any versions of all plugins published by the upstream source. If any versions are found, they will be queued for download.

If the plugin is not currently installed in the update center the Plugin Versioning Strategy (see ???) will

If any of the plugins are set to set to track the Latest version and one of the downloaded versions is newer than the current latest version, then this will result in the newer version being immediately published once the download has been completed. (See the section called “Version number rules” for a description of how version numbers are compared by Jenkins.)

If a plugin is set to either None or a specific version, then no change to the published version will take place.