Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-921

New plugin release shows up in https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ but not in https://updates.jenkins-ci.org/current/update-center.json

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      New plugin release for absint-astree-plugin shows up in https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/
      Release was more than 48 hours ago, but plugin is still not listed in/on https://updates.jenkins-ci.org/current/update-center.json

      Maven release (mvn release:prepare release:perform ) reported success and plugin build is on the repo server, as said.

      Likely related, the jenkins-plugin-info entry in the plugin's Wiki page does not work.

      Did we miss a step of the release process or is this some infrastructure issue?

        Attachments

          Activity

          Hide
          orrc Christopher Orr added a comment -

          The problem is with the generation of the Update Centre metadata, which is somewhat caused by the weird URL handling of the Confluence wiki.

          Even although you've done everything correct, the listed wiki URL technically isn't correct. Because the wiki page title has an accent in it, Confluence gives such pages a different canonical URL, in this case: https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=99910545

          This causes the Update Centre generator to ignore your plugin, as the given wiki URL doesn't match with what the generator gets from the Confluence API. That's an edge case that we don't handle properly as the moment, and so I've filed an infrastructure bug (INFRA-922), and added a manual override of the URL for your plugin: https://github.com/jenkinsci/backend-update-center2/pull/75

          Once that Pull Request gets merged, your plugin will appear in the Update Centre (and the wiki infobox will appear, as it's based on the UC metadata).

          Show
          orrc Christopher Orr added a comment - The problem is with the generation of the Update Centre metadata, which is somewhat caused by the weird URL handling of the Confluence wiki. Even although you've done everything correct, the listed wiki URL technically isn't correct. Because the wiki page title has an accent in it, Confluence gives such pages a different canonical URL, in this case: https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=99910545 This causes the Update Centre generator to ignore your plugin, as the given wiki URL doesn't match with what the generator gets from the Confluence API. That's an edge case that we don't handle properly as the moment, and so I've filed an infrastructure bug ( INFRA-922 ), and added a manual override of the URL for your plugin: https://github.com/jenkinsci/backend-update-center2/pull/75 Once that Pull Request gets merged, your plugin will appear in the Update Centre (and the wiki infobox will appear, as it's based on the UC metadata).
          Hide
          danielbeck Daniel Beck added a comment -

          I wonder whether using the canonical URL in the pom would work as a permanent workaround.

          Show
          danielbeck Daniel Beck added a comment - I wonder whether using the canonical URL in the pom would work as a permanent workaround.
          Hide
          orrc Christopher Orr added a comment -

          Sure, that would work just the same as the wiki URL override. But it would fix the problem only for this plugin. Not that this happens often

          Show
          orrc Christopher Orr added a comment - Sure, that would work just the same as the wiki URL override. But it would fix the problem only for this plugin. Not that this happens often
          Hide
          orrc Christopher Orr added a comment -

          Plugin is now available in the Update Centre.

          Show
          orrc Christopher Orr added a comment - Plugin is now available in the Update Centre.
          Hide
          danielbeck Daniel Beck added a comment -

          Christopher Orr Still, would cut down on the number of special cases handled by backend-update-center2 if the pom were fixed.

          So I recommend this be fixed in the POM towards the next plugin release so we can delete the rewrite workaround.

          Show
          danielbeck Daniel Beck added a comment - Christopher Orr Still, would cut down on the number of special cases handled by backend-update-center2 if the pom were fixed. So I recommend this be fixed in the POM towards the next plugin release so we can delete the rewrite workaround.

            People

            • Assignee:
              orrc Christopher Orr
              Reporter:
              absint Technical Support
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: