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

Purge existing references to maven/maven2.jenkins-ci.org from plugin POMs

    Details

    • Similar Issues:

      Description

      In order to fully sunset the maven.jenkins-ci.org and maven2.jenkins-ci.org virtual hosts, now which only redirect to repo.jenkins-ci.org, we need to update some POMs like this one.

        Attachments

          Issue Links

            Activity

            Show
            danielbeck Daniel Beck added a comment - https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L760
            Show
            danielbeck Daniel Beck added a comment - https://github.com/jenkinsci/maven-hpi-plugin/pull/34
            Hide
            danielbeck Daniel Beck added a comment -

            R. Tyler Croy Due to how the plugin parent POMs work, it's not possible to mechanically update to newer versions and batch push changes into plugin repositories.

            If you want to get rid of the host name, documenting the issue that plugin POMs ≤2.3 will need to be updated or override the repository location is the best we can do. Since most users seem to suffer from INFRA-588 already anyway, this probably doesn't make things a lot worse.

            Show
            danielbeck Daniel Beck added a comment - R. Tyler Croy Due to how the plugin parent POMs work, it's not possible to mechanically update to newer versions and batch push changes into plugin repositories. If you want to get rid of the host name, documenting the issue that plugin POMs ≤2.3 will need to be updated or override the repository location is the best we can do. Since most users seem to suffer from INFRA-588 already anyway, this probably doesn't make things a lot worse.
            Hide
            rtyler R. Tyler Croy added a comment -

            It's been a few months, is this resolvable finally? crosses fingers

            Show
            rtyler R. Tyler Croy added a comment - It's been a few months, is this resolvable finally? crosses fingers
            Hide
            olivergondza Oliver Gondža added a comment -

            It is supper annoying merging a pull request and finding out the plugin refers to old repo while trying to release. It would be great if we manage to update the poms in plugins itself. There seems to be some low hanging fruit for poms that uses plugin-pom and contains some expected declarations.

            Show
            olivergondza Oliver Gondža added a comment - It is supper annoying merging a pull request and finding out the plugin refers to old repo while trying to release. It would be great if we manage to update the poms in plugins itself. There seems to be some low hanging fruit for poms that uses plugin-pom and contains some expected declarations.
            Hide
            danielbeck Daniel Beck added a comment -

            I'd like to see the 2.x line of plugin POMs adopted widely. Unfortunately, it's not realistic to mechanically update all plugins to that AFAICT. And just overriding the distributionManagement repos seems hackish.

            Show
            danielbeck Daniel Beck added a comment - I'd like to see the 2.x line of plugin POMs adopted widely. Unfortunately, it's not realistic to mechanically update all plugins to that AFAICT. And just overriding the distributionManagement repos seems hackish.
            Hide
            batmat Baptiste Mathus added a comment -

            From my experience, I concur: totally impossible to do that automatically.

            The only thing we could do quite easily is have that list. It woud require cloning every single repos (well, pom.xml should be enough), and run mvn help:effective-pom on those and grep maven.jenkins-ci.org in there. We would then have a list of to-be-updated plugins. Then we could decide to try and fix the most important/installed or so.

            At least this easy step would give us data to plan for the changes/PR per-se.

            Show
            batmat Baptiste Mathus added a comment - From my experience, I concur: totally impossible to do that automatically. The only thing we could do quite easily is have that list. It woud require cloning every single repos (well, pom.xml should be enough), and run mvn help:effective-pom on those and grep maven.jenkins-ci.org in there. We would then have a list of to-be-updated plugins. Then we could decide to try and fix the most important/installed or so. At least this easy step would give us data to plan for the changes/PR per-se.
            Hide
            danielbeck Daniel Beck added a comment -

            Haven't seen this come up in a while, so probably not worth doing.

            Show
            danielbeck Daniel Beck added a comment - Haven't seen this come up in a while, so probably not worth doing.

              People

              • Assignee:
                danielbeck Daniel Beck
                Reporter:
                rtyler R. Tyler Croy
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: