-
Bug
-
Resolution: Fixed
-
Major
-
None
-
jenkins-2.5
Implementation of JENKINS-34674 was not completely correct.
DEFAULT_SITE_ID has too wide effect.
Expected behavior:
- Jenkins uses another update site as a default one
Actual behavior:
- Jenkins renames the default update site to DEFAULT_SITE_ID
- Jenkins still uses this update site as a default, because it's the first in the list
Workaround: When adding an custom UpdateSite in the code, delete the default site from the list, rename default site to the original ID, then add it back.
- is related to
-
JENKINS-34674 Support configurable Default Update center IDs
-
- Resolved
-
Description of my case, where I get into the issue:
1) I have 2 update centers. "my-uc" and "default". Default points to Jenkins OSS, "my-uc" - to my site. "my-uc" is added by the code, it does not modify UpdateCenter settings
2) In System properties I set DEFAULT_UC_ID to "my-uc"
3) When Jenkins initializes the instance, it takes the default settings from update center and creates it as "my-uc"
4) When my code adds the real "my-uc" site, there is a conflict