I believe I was initially swayed by the fact that there are a couple of places in the core where the default site is forced to be first site in the UpdatSite list:

This actually has the effect of putting the jenkinsci default site as the first one in the UI even though it is not the first in the config file. Updating the URL from UI alters the URL in the persisted config file but does not change its site order. Seems a bit confusing.

In any event, Daniel, you are right!

If I use the update center's self-reported ID as its ID in Jenkins, as follows:

<?xml version='1.0' encoding='UTF-8'?>
<sites>
  <site>
    <id>company-default</id>
    <url>https://update-center.company.com/update-center.json</url>
  </site>
  <site>
    <id>default</id>
    <url>http://updates.jenkins-ci.org/stable/update-center.json</url>
  </site>

Then as long as https://update-center.company.com/update-center.json uses company-default as its ID, the corporate blessed plugin scenario works!

I will resolve this issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to