Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15720

Deploy Artifacts to Maven Repository only resolves Repository ID against POM, not settings.xml

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • maven-plugin
    • None
    • Platform independent

      The "Deploy artifacts to maven repository" action allows for specification of the repository id to name the deploy target. If a respective repository is specified in the projects pom, the id is successfully resolved to the corresponding URL an deploy succeeds. If, however, the repository is specified only in the (global or user) settings.xml file, it is resolved.

      I see that there is an acceptable workaround and repository URL tend not to change to often, but it would still be nice not to have to retype it for every job. And if you ever have to migrate to a new server, as I just did, it would save some annoyance with correcting the URL in each and every job!

          [JENKINS-15720] Deploy Artifacts to Maven Repository only resolves Repository ID against POM, not settings.xml

          Daniel Barth added a comment -

          Wrong plugin!
          This is deploy war/ear to container.

          Daniel Barth added a comment - Wrong plugin! This is deploy war/ear to container.

          Daniel Barth added a comment -

          Hm, just wanted to remove Component/s: deploy...

          Daniel Barth added a comment - Hm, just wanted to remove Component/s: deploy...

          Sven Amann added a comment -

          There is no deploy war/ear to container component... how is it called?

          Sven Amann added a comment - There is no deploy war/ear to container component... how is it called?

            Unassigned Unassigned
            salsolatragus Sven Amann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: