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

When using withMaven, "mvn deploy" no longer uploads artifacts to Nexus.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • pipeline-maven-plugin
    • None

      When using withMaven within my pipeline's constructs, the deploy plugin no longer tries to upload artifacts to Nexus. If I remove (comment out) the withMaven block, everything goes back to normal and deployment works.

      However, I obviously lose all the publishers I'm interested in (JUnit, JaCoCo, etc.). I'm using withMaven() { ... }  (i.e. default mode, no special options or constructs).

      In particular, I very strongly desire to not store actual build artifacts in Jenkins since they're already meant to be housed in Nexus (i.e. why double-store?).

      I need Maven to be the "agent" performing the upload to Nexus since the target repository may change "dynamically" depending on certain criteria (i.e. a Maven profile that gets activated based on envvars and such) and special circumstances (we're working to remove this, but for now it's a requirement).

      The deploy plugin in use is 3.1.1, but also fails with 2.7.

            Unassigned Unassigned
            drivera Diego
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: