Right now the plugin does not update the maven-metadata.xml and such the version information of the uploaded artifacts is not available for use in other jobs.

          [JENKINS-40656] Update maven-metadata.xml after upload

          Suresh Kumar added a comment -

          Tried creating maven2 type repository allowing both SNAPSHOT & RELEASE, when we upload Release type of artifact it is not creating maven-metadata.xml. Tried to upload the SNAPSHOT type of artifact it is creating maven-metadata.xml and updated.

          Try once as explained above and let me know whether the behavior is expected one or not.

          Thanks

          Suresh Kumar added a comment - Tried creating maven2 type repository allowing both SNAPSHOT & RELEASE, when we upload Release type of artifact it is not creating maven-metadata.xml. Tried to upload the SNAPSHOT type of artifact it is creating maven-metadata.xml and updated. Try once as explained above and let me know whether the behavior is expected one or not. Thanks

          Jason Hull added a comment -

          This is a bug, not a new feature. I recently upgraded the plugin from 2.3 to 2.9 and now I notice that the Maven metadata is not being updated. Am I correct that this used to work?

          Jason Hull added a comment - This is a bug, not a new feature. I recently upgraded the plugin from 2.3 to 2.9 and now I notice that the Maven metadata is not being updated. Am I correct that this used to work?

          Suresh Kumar added a comment -

          jhull123
          Share the details of the Nexus version and Repository configuration.

          Suresh Kumar added a comment - jhull123 Share the details of the Nexus version and Repository configuration.

          I can limit the problem to plugin version 2.5 to 2.7. It is still working with plugin 2.4, but already fails with 2.7.

          Nexus Repository Manager OSS 2.13.0-01

          Repo type: hosted

          Provider: Maven2

          Format: maven2

          Policy: Release

          Stefan Callsen added a comment - I can limit the problem to plugin version 2.5 to 2.7. It is still working with plugin 2.4, but already fails with 2.7. Nexus Repository Manager OSS 2.13.0-01 Repo type: hosted Provider: Maven2 Format: maven2 Policy: Release

          Lars Briem added a comment -

          It looks like I have the same issue with version 3.17. I upload a jar to nexus. For snapshot versions, a maven-metadata.xml file is generated in the corresponding version folder, for release versions it is not. In the folder of the artifact, there is no maven-metadata.xml file generated. This might be the reason, why I am not able to resolve dynamic versions.

          Is there any workaround available to fix this problem?

          Lars Briem added a comment - It looks like I have the same issue with version 3.17. I upload a jar to nexus. For snapshot versions, a maven-metadata.xml file is generated in the corresponding version folder, for release versions it is not. In the folder of the artifact, there is no maven-metadata.xml file generated. This might be the reason, why I am not able to resolve dynamic versions. Is there any workaround available to fix this problem?

          rives davy added a comment - - edited

          September 2020 and still having this issue with version 2.10... Jenkins is made for CICD, uploading artifact is heart of CICD, how a such issue can be ignored for so long.

          rives davy added a comment - - edited September 2020 and still having this issue with version 2.10... Jenkins is made for CICD, uploading artifact is heart of CICD, how a such issue can be ignored for so long.

            pskumar448 Suresh Kumar
            extenzy Bogdan Suta
            Votes:
            5 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: