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

Maven Spy seems to swallow transport warnings

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • pipeline-maven-plugin
    • None

      Maven CLI prints this if I give wrong credentials:

      [WARNING] Could not transfer metadata org.apache.maven.plugins:maven-help-plugin/maven-metadata.xml from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/): Not authorized , ReasonPhrase:Unauthorized.

      Trying to run a maven-pipeline build against a mirror requiring authentication fails in this way:

      13:33:21 + mvn help:effective-settings
13:33:21 ----- withMaven Wrapper script -----
[ ... SNIP ...  ]
13:33:22 [jenkins-maven-event-spy] INFO generate /home/acme/workspace/ent-classification_BLD-2798-EVNDRW5B2OELJDWRHOFPU56LTM6EP34GPWNMP6QHXLZD72W5RS7Q@tmp/withMaven7c261ec7/maven-spy-20170705-133320-937.log ...
13:33:22 [INFO] Scanning for projects...

13:33:23 [INFO] Downloading: https://readonly-mvnrepo.acme-internal.com/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom
13:33:23 [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:2.5: Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5

      The "Invoke Top-Level Maven Targets" step would print the warning

          [JENKINS-45314] Maven Spy seems to swallow transport warnings

          Jakub Bochenski added a comment -

          This is actually working. The local user got synched with LDAP just as I was testing the pipeline plugin.

          Jakub Bochenski added a comment - This is actually working. The local user got synched with LDAP just as I was testing the pipeline plugin.

          Jakub Bochenski added a comment -

          PS. It would be nice if the console output reported the HTTP error though. Maven CLI prints this if I give wrong credentials:

          [WARNING] Could not transfer metadata org.apache.maven.plugins:maven-help-plugin/maven-metadata.xml from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/): Not authorized , ReasonPhrase:Unauthorized.

          Jakub Bochenski added a comment - PS. It would be nice if the console output reported the HTTP error though. Maven CLI prints this if I give wrong credentials: [WARNING] Could not transfer metadata org.apache.maven.plugins:maven-help-plugin/maven-metadata.xml from/to internal-repo (https: //readonly-mvnrepo.acme-internal.com/): Not authorized , ReasonPhrase:Unauthorized.

          Jakub Bochenski added a comment -

          Missed my own comment, changed the ticket to be an improvement for error logging

          Jakub Bochenski added a comment - Missed my own comment, changed the ticket to be an improvement for error logging

            Unassigned Unassigned
            jbochenski Jakub Bochenski
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: