Uploaded image for project: 'Jenkins Artifactory Plug-in'
  1. Jenkins Artifactory Plug-in
  2. HAP-61

"Deploy artifacts to Artifactory" - provide include/exclude patterns

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3.6
    • Component/s: Maven2
    • Labels:
      None

      Description

      Today, after job finishes, Hudson plugin deploys all Maven artifacts to Artifactory. Sometimes, it deploys things we don't really need there but Maven marked them as "artifacts" anyway.

      For example, our POM creates a large binary "*.tar.gz" file. It still has "<packaging>jar</packaging>" so a small *.jar file is also created, we usually have it set to

      <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-jar-plugin</artifactId>
          <configuration>
              <includes>
                  <include>nothing</include>
              </includes>
          </configuration>
      </plugin>
      

      So this small *.jar file and the POM itself ares till deployed to Artifactory even though we really don't need it there.
      Sometimes, our POM doesn't even create a new "*.tar.gz" archive for various reasons but we still have this "noise" deployed to Artifactory.

      If Hudson plugin had an "include pattern" it could nicely solve this issue as it would only deploy the real data and not something Maven happens to see as an "artifact".

      Thank you!

        Attachments

          Activity

            People

            • Assignee:
              noam.tenne Noam Y. Tenne (Inactive)
              Reporter:
              evgenygoldin Evgeny Goldin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: