Artifactory Plugin

 

Plugin Information

Plugin ID artifactory
Latest Release 3.0.5
Latest Release Date Dec 16, 2013
Sources [External| ]
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla

This plugin allows deploying Maven 2, Maven 3, Ivy and Gradle artifacts and build info to the Artifactory artifacts manager.

Reporting Issues
Issues for this plugin are managed primarily on the plugin's project under the JFrog JIRA.
Managing independent release versions and having sub-components for each build technology requires the plugin to be a first-level JIRA project, which is currently not possible under the Hudson-provided JIRA.

Introduction

The Hudson Artifactory Plugin brings Artifactory's Build Integration support to Hudson. This integration allows your build jobs to deploy artifacts automatically to Artifactory and have them linked to the build job that created them.
As part of deployment additional information is recorded by the plugin to give you full visibility of deployed artifacts, used dependencies and information about original build environment. As an important side affect the plugin also supports optimized end-of-build-only deployment.
To learn more about the Artifactory-side of the Hudson Artifactory Plugin, please read the documentation on the JFrog wiki.

Requirements

This plugin requires Artifactory 2.2.3 or later and Hudson 1.358 or later.
The plugin currently supports Maven 2, Maven 3, Gradle and Ivy-Ant builds.

Configuring Artifactory Server(s)

First, we need to configure the Artifactory server(s) that we will use to deploy artifacts and build info to. We do this on Hudson's system configuration page (Manage Hudson -> Configure System).
Locate the "Artifactory servers" configuration section, click the "Add" button and fill-in the Artifactory url and optionally a username and password that will be used to query Artifactory for a list of target repositories (this is only required if Artifactory is configured not to allow anonymous access).

You can also set the default deployer credentials (and the default resolver credentials used by some build types) that will be used by individual jobs when publishing and resolving to/from Artifactory.

Configuring Maven 2 and Maven 3 Builds

Once at least one Artifactory server is configured we can add the plugin as a post-build step in a Maven 2/3 build. To do this, create or edit a Maven 2/3 build project.

Maven 3 Support for Hudson < v1.392
The Hudson Artifactory plugin supports running Maven 3 builds in older versions of Hudson using free-style jobs, using a Maven 3 build step for running a Maven 3 installation configured in the general Hudson configuration, and a build environment section for the Artifactory Maven 3 integration (artifact and build information deployment). This feature is deprecated with newer versions of Hudson, so for Maven 3 builds users are encouraged to configure the Artifactory integration using Hudson's native Maven 2/3 build projects, as explained above.

Configuring Gradle Builds

You can use the Hudson Gradle Plugin (configured under a free-style job) in conjunction with the Hudson Artifactory Plugin and have your Gradle builds resolve artifacts from Artifactory and deploy artifacts and build information to Artifactory.

Configuring Ivy-Ant Builds

By using the Hudson Ivy Plugin together with the Hudson Artifactory Plugin your Ivy builds will publish artifacts and build information to Artifactory whenever an ivy:publish task is executed.

Install the Hudson Ivy Plugin
To use the Hudson Artifactory Plugin with Ivy builds you need to install the Hudson Ivy Plugin.

Publishing to your local file cache repository is the best way to go (i.e. you do not need to publish to Artifactory). The plugin will intercept the publish events and will replay them against Artifactory according to the configuration. Using an ivy:publish task that publishes directly to Artifactory will result in (redundant) double publishing.

License Control

You use the Artifactory Pro License Control feature to discover and handle third party dependency licensing issues as part of the build.
Check the 'Run license checks' option if wish that Artifactory will scan and check the licenses of all dependencies used by this build. If you wish to inform selected users about any license violations detected while scanning, you may enter a white-spaced list of e-mail addresses to the notification recipients text box.

Watch the Screencast

To see the Hudson Artifactory Integration in action you can watch the following screencast.

Changelog

1.4.2 (27 Jan 2011)

  1. The plugin now works with Hudson's new native Maven 3 jobs (HAP-130, HAP-131)

1.4.1 (10 Jan 2011)

  1. Synchronize the build retention policy in Artifactory with Hudson's build retention settings (requires Artifactory Pro) (HAP-90)

1.4.0 (09 Jan 2011)

  1. Improved Gradle support
  2. Optimized checksum-based publishing with Artifactory 2.3.2+ that saves redeploying the same binaries (RTFACT-3808)
  3. Remote agent support for Gradle, Maven 3 and Ivy builds (HAP-59, HAP-60, HAP-114)
  4. Configurable ivy/artifact patterns for Ivy builds (HAP-120)

1.3.6 (21 Nov 2010)

  1. Allow specifying include/exclude patterns for published artifacts (HAP-61).
  2. Support for custom Ivy/artifact patterns for Gradle published artifacts (HAP-108).

1.3.5 (7 Nov 2010)

  1. Fixed integration with Hudson maven release plugin. (HAP-93)
  2. Global Artifactory credentials (HAP-53)
  3. Auto preselect target release and snapshot repositories. (HAP-98)

1.3.4 (28 Oct 2010)

  1. Fixed Gradle support

1.3.3 (21 Oct 2010)

  1. Update version of the Gradle extractor.

1.3.2 (19 Oct 2010)

  1. Support for running license checks on third-party dependencies and sending license violation email notifications (HAP-91)

1.3.1 (19 Sep 2010)

  1. Maven 2 and Maven 3 support two target deploy repositories - releases and snapshots (HAP-29)
  2. Maven 2 - Allow deployment even if the build is unstable (HAP-77)
  3. Link to the build info next to each build that deployed build info (HAP-80)
  4. Link to the builds list in the jobs' main page (HAP-41)
  5. Allow skipping the creation and deployment of the build info (HAP-47)

1.3.0 (26 Aug 2010)

  1. New support for Maven 3 Beta builds!

1.2.0 (26 Jul 2010)

  1. New support for Ivy builds! (many thanks to Timo Bingaman for adding the hooks to the the Hudson Ivy Plugin)
  2. Supporting incremental builds (HAP-52)
  3. Testing connection to Artifactory in the main configuration page
  4. Update Hudson dependency to version 1.358
  5. Fixed HAP-51 - tar.gz files were deployed as .gz files

1.1.0 (09 Jun 2010)

  1. Added support for gradle jobs, see: http://www.jfrog.org/confluence/x/tYK5
  2. Connection timeout setting changed from milliseconds to seconds.
  3. Allow bypassing the http proxy (HUDSON-5892)

1.0.7 (04 Mar 2010)

  1. Improved Artifactory client
  2. Another fix for duplicate pom deployments
  3. Sending parent (upstream) build information
  4. Displaying only local repositories when working with Artifactory 2.2.0+

1.0.6 (16 Feb 2010)

  1. Fixed a bug in the plugin that in some cases skipped deployment of attached artifacts
  2. In some cases, pom were deployed twice
  3. MD5 hash is now set on all files
  4. Dependency type is passed to the build info

1.0.5 (22 Jan 2010)

  1. Using Jackson as JSON generator for BuildInfo (will fix issues with Hudson version 1.340-1.341)

1.0.4 (15 Jan 2010)

  1. Accept Artifactory urls with slash at the end
  2. Fixed JSON object creation to work with Hudson 1.340

1.0.3 (07 Jan 2010)

  1. Using preemptive basic authentication

1.0.2 (22 Dec 2009)

  1. Configurable connection timeout

1.0.1 (16 Dec 2009)

  1. Fixed Artifactory plugin relative location (for images and help files)

1.0.0 (14 Dec 2009)

  1. First stable release

Labels:

plugin-upload plugin-upload Delete
tier3-compat-plugin tier3-compat-plugin Delete
tier3-hudson-plugin tier3-hudson-plugin Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. Dec 19, 2009

    Thomas Trepper says:

    Hi all, after configuring the servers in the hudson system-configuration it add...

    Hi all,

    after configuring the servers in the hudson system-configuration it added the artifactory-plugin as a build-step in a particulary job, but there is no other action I can check, especially a post-build-action as shown in the picture. If I try to apply with the plugin added as build-step, I get the following stack-trace:

    org.kohsuke.stapler.NoStaplerConstructorException: Unable to find org/jfrog/hudson/ArtifactoryBuilder.stapler. There's no @DataBoundConstructor on any constructor of class org.jfrog.hudson.ArtifactoryBuilder
    at org.kohsuke.stapler.RequestImpl.loadConstructorParamNames(RequestImpl.java:471)
    at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:329)
    at hudson.model.Descriptor.newInstance(Descriptor.java:351)
    at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:633)
    at hudson.util.DescribableList.rebuildHetero(DescribableList.java:164)
    at hudson.model.Project.submit(Project.java:194)
    at hudson.model.FreeStyleProject.submit(FreeStyleProject.java:97)
    at hudson.model.Job.doConfigSubmit(Job.java:967)
    at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:519)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:185)
    at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:101)
    at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:54)
    at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:74)
    at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:30)
    at org.kohsuke.stapler.Stapler.invoke(Stapler.java:492)
    at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:180)
    at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:30)
    at org.kohsuke.stapler.Stapler.invoke(Stapler.java:492)
    at org.kohsuke.stapler.Stapler.invoke(Stapler.java:408)
    at org.kohsuke.stapler.Stapler.service(Stapler.java:117)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
    at winstone.ServletConfiguration.execute(ServletConfiguration.java:249)
    at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
    at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
    at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94)
    at org.jvnet.hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:47)
    at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97)
    at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86)
    at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
    at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
    at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
    at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
    at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
    at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
    at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
    at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
    at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
    at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
    at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
    at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
    at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
    at java.lang.Thread.run(Thread.java:619)

    Did I miss anything? (Hudson 1.337; Artifactory 2.1.2; Plugin 1.0.1)

    1. Dec 20, 2009

      Yossi Shaul says:

      I tested the plugin with version 1.337 and it works fine. Did you restarted the ...

      I tested the plugin with version 1.337 and it works fine. Did you restarted the server after installation? Any exception during installation of the plugin or hudson startup?
      And BTW, the plugin works with Artifactory version 2.1.3 which will be released soon (but it is not related to the problem you are experiencing).

  2. Jan 19, 2010

    David Cloutier says:

    Hi, I've just installed the plugin, I've setup the artifactory URL from the "co...

    Hi,

    I've just installed the plugin, I've setup the artifactory URL from the "configure hudson" page but in the "configure Job" page there are no "repositories".

    How do I add them?

    Thanks,

    Dave.

    1. Jan 20, 2010

      Yossi Shaul says:

      You'll only see the repositories list if you configured a good Artifactory URL a...

      You'll only see the repositories list if you configured a good Artifactory URL and used the right credentials. Please make sure you configured it correctly. You can contact me directly if still doesn't work.

    2. Feb 11, 2010

      developer says:

      Hi, I had a similar issue and couldn't see any repositories. URL was correctly...

      Hi,
      I had a similar issue and couldn't see any repositories.
      URL was correctly, user and password was correctly and I also tried out to set everything to public and give anonymous full permissions,
      nothing helped.

      I have upgraded to the latest artifactory 2.2.0 then it worked fine.
      Before it was using 2.1.1 and I didn't read the requirements 2.1.3

      Cheers

  3. Jan 22, 2010

    mmorizot says:

    hi, We're now using hudson 1.341, the artifactory plugin 1.04 and artifactory 2...

    hi,

    We're now using hudson 1.341, the artifactory plugin 1.04 and artifactory 2.1.3.

    When deploying the build infos to artifactory we constantly have  (any idea where this can come from?):

    If i deploy using a mix of "hudson maven repo deploy plugin" and "hudson artifactory deploy only build info" , i get :

    [INFO] Retrieving previous build number from scm-repository-hudson
    [INFO] Uploading project information for xml-configuration 2.1.2-SNAPSHOT
    [INFO] Retrieving previous metadata from scm-repository-hudson
    [INFO] Uploading repository metadata for: 'snapshot GID:xml-configuration:2.1.2-SNAPSHOT'
    [INFO] Retrieving previous metadata from scm-repository-hudson
    [INFO] Uploading repository metadata for: 'artifact GID:xml-configuration'
    Deploying build info to: http://MYSERVER/artifactory/api/build
    ERROR: Failed to send build info: OK
    java.io.IOException: Failed to send build info: OK
    at org.jfrog.hudson.BuildInfoDeployer.sendBuildInfo(BuildInfoDeployer.java:176)
    at org.jfrog.hudson.BuildInfoDeployer.deploy(BuildInfoDeployer.java:53)
    at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:101)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
    at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:582)
    at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:563)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:594)
    at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:534)
    at hudson.model.Run.run(Run.java:1216)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:122)

    using artifacory to deploy and upload build info, we get :
    Deploying build info to: http://MYSERVER/artifactory/api/build
    ERROR: Failed to send build info: Internal Server Error
    java.io.IOException: Failed to send build info: Internal Server Error
    at org.jfrog.hudson.BuildInfoDeployer.sendBuildInfo(BuildInfoDeployer.java:176)
    at org.jfrog.hudson.BuildInfoDeployer.deploy(BuildInfoDeployer.java:53)
    at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:101)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
    at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:582)
    at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:563)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:594)
    at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:534)
    at hudson.model.Run.run(Run.java:1216)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:122)

    1. Jan 22, 2010

      Yossi Shaul says:

      Update the plugin to version 1.0.5. That should fix it.

      Update the plugin to version 1.0.5. That should fix it.

      1. Feb 04, 2010

        Alexander Reelsen says:

        Hi, I am using version 1.0.5 and also get this at a first test: Deploying arti...

        Hi,

        I am using version 1.0.5 and also get this at a first test:

        Deploying artifacts to http://192.168.120.65:40000/artifactory/XYZREPO
        Deploying artifacts of module: com.XYZ.mp:mp-authorization
        Deploying artifact: http://192.168.120.65:40000/artifactory/XYZREPO/com/XYZ/mp/mp-authorization/3.1.1-SNAPSHOT/mp-authorization-3.1.1-SNAPSHOT.pom;build.name=MP+authorization;build.number=15
        Deploying artifact: http://192.168.120.65:40000/artifactory/XYZREPO/com/XYZ/mp/mp-authorization/3.1.1-SNAPSHOT/mp-authorization-3.1.1-SNAPSHOT.pom;build.name=MP+authorization;build.number=15
        Deploying build info to: http://192.168.120.65:40000/artifactory/XYZREPO/api/build
        ERROR: Failed to send build info: OK
        java.io.IOException: Failed to send build info: OK
            at org.jfrog.hudson.BuildInfoDeployer.sendBuildInfo(BuildInfoDeployer.java:179)
            at org.jfrog.hudson.BuildInfoDeployer.deploy(BuildInfoDeployer.java:56)
            at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:101)
            at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
            at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:582)
            at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:563)
            at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:594)
            at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
            at hudson.model.Run.run(Run.java:1221)
            at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
            at hudson.model.ResourceController.execute(ResourceController.java:88)
            at hudson.model.Executor.run(Executor.java:122)
        Finished: FAILURE

        Any hints on configuration mistakes on my part?

        Thanks a lot for helping!

        1. Feb 11, 2010

          developer says:

          Hi, I had some similar issue but already using 1.0.5 saying Deploying build in...

          Hi,
          I had some similar issue but already using 1.0.5 saying

          Deploying build info to: http://vslpnms1.arvato-systems.de:8080/artifactory/libs-snapshots-local/api/build
          ERROR: Failed to send build info: Forbidden
          java.io.IOException: Failed to send build info: Forbidden

          Everything was allowed to anonymous

          I have upgraded to the latest artifactory 2.2.0 then it worked fine.
          Before it was using 2.1.1 and I didn't read the requirements 2.1.3

          Cheers

  4. Feb 11, 2010

    developer says:

    Hi folks, I just tried out the latest artifactory plugin v1.05 joining the lates...

    Hi folks,
    I just tried out the latest artifactory plugin v1.05 joining the latest hudson v1.345 and the latest artifactory v2.2.0
    and saw that the artifactory plugin leaves out some artifacts that have been build!!

    For instance javadoc.jar, sources.jar and several other artifacts like asseblies xxx.zip or xxx.exe types.
    Only foo.jar, foo-test.jar and pom.xml is deployed.

    Example: Hudson shows the full lists of build artifacts correctly:

    Build Artifacts
    bic_services_1.0.32.0-SNAPSHOT-javadoc.jar
    bic_services_1.0.32.0-SNAPSHOT-sources.jar
    bic_services_1.0.32.0-SNAPSHOT-tests.jar
    bic_services_1.0.32.0-SNAPSHOT.jar
    pom.xml

    Now if the assebly plugin starts it looks like this:

    Deploying artifacts of module: some:bic_services
    Deploying artifact: http://foo/artifactory/libs-snapshots-local/foo/bic_services/1.0.32.0-SNAPSHOT/bic_services-1.0.32.0-SNAPSHOT.jar;build.name=FOO+%28daily%29;build.number=285
    Deploying artifact: http://foo/artifactory/libs-snapshots-local/foo/bic_services/1.0.32.0-SNAPSHOT/bic_services-1.0.32.0-SNAPSHOT.pom;build.name=FOO+%28daily%29;build.number=285
    Deploying artifact: http://foo/artifactory/libs-snapshots-local/foo/bic_services/1.0.32.0-SNAPSHOT/bic_services-1.0.32.0-SNAPSHOT-.jar;build.name=FOO+%28daily%29;build.number=285
    Deploying artifact: http://foo/artifactory/libs-snapshots-local/foo/bic_services/1.0.32.0-SNAPSHOT/bic_services-1.0.32.0-SNAPSHOT-tests.jar;build.name=FOO+%28daily%29;build.number=285

    Ass you can see in the output:

    bic_services_1.0.32.0-SNAPSHOT-javadoc.jar
    bic_services_1.0.32.0-SNAPSHOT-sources.jar

    are missing.

    Instead there is some unamed one stopping after the last hyphen called:
    bic_services-1.0.32.0-SNAPSHOT-.jar;

    If I use the maven deploy command everything works correctly.
    If I use the artifactory plugin the artifacts from above are missing and are not updated in the artifactory.

    Any help is welcome
    developer

  5. Feb 16, 2010

    Paul Harris says:

    Hi, Is there any chance you can add an option to ignore/bypass the Hudson proxy...

    Hi,

    Is there any chance you can add an option to ignore/bypass the Hudson proxy (in the Hudson Update Center).  It looks like all artifactory plugin requests all go via this proxy (if configured) and I cannot get a list of repositories unless I remove the proxy config.

    My artifactory is located on our local network and our stupid proxy blocks requests to it for some reason.   I will try asking our network guys but I have more confidence in you being able to provide a fix than them..

    I seem to remember a similar problem with another plugin making use of the Hudson proxy config.   Maybe Hudson should provide a noProxyHosts option to make this more viable for plugins to use.

    Thanks a lot.

    1. Mar 08, 2010

      dfme says:

      We have excactly the same issue. Alread when setting up Artifactory for a build ...

      We have excactly the same issue. Alread when setting up Artifactory for a build the 'Target repository' list is empty. We also have configured Hudson to use a proxy for updating over the Internet. However Artifactory and Hudson are running on the same machine so there is no need for the artifactory plugin to go over the proxy.

      Could this be fixed?

      1. Mar 10, 2010

        Yossi Shaul says:

        Sure, I'll add it to the next plugin release. You can track it at: http://issues...

        Sure, I'll add it to the next plugin release. You can track it at: http://issues.hudson-ci.org/browse/HUDSON-5892

  6. Jun 17, 2010

    Filip Blondeel says:

    Hi all, Recently I upgraded Hudson to version 1.362 and the artifactory plugin ...

    Hi all,

    Recently I upgraded Hudson to version 1.362 and the artifactory plugin to version 1.1.0, but now I get an error from the artifactory plugin when it's trying to deploy the build info to Artifactory:Deploying build info ...
    ERROR: Invalid use of SingleClientConnManager: connection still allocated.
    Make sure to release the connection before allocating another one.
    java.lang.IllegalStateException: Invalid use of SingleClientConnManager: connection still allocated.
    Make sure to release the connection before allocating another one.
    at org.apache.http.impl.conn.SingleClientConnManager.getConnection(SingleClientConnManager.java:199)
    at org.apache.http.impl.conn.SingleClientConnManager$1.getConnection(SingleClientConnManager.java:173)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:356)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
    at org.jfrog.build.client.PreemptiveHttpClient.execute(PreemptiveHttpClient.java:75)
    at org.jfrog.build.client.ArtifactoryBuildInfoClient.sendBuildInfo(ArtifactoryBuildInfoClient.java:209)
    at org.jfrog.hudson.BuildInfoDeployer.deploy(BuildInfoDeployer.java:58)
    at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:110)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
    at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601)
    at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:598)
    at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
    at hudson.model.Run.run(Run.java:1276)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:124)

    Has anyone else encountered this problem ?

  7. Jun 17, 2010

    Filip Blondeel says:

    Hi all, Recently I upgraded Hudson to version 1.362 and the artifactory plugin t...

    Hi all,
    Recently I upgraded Hudson to version 1.362 and the artifactory plugin to version 1.1.0, but now I get an error from the artifactory plugin when it's trying to deploy the build info to Artifactory:
    Deploying build info ...
    ERROR: Invalid use of SingleClientConnManager: connection still allocated.
    Make sure to release the connection before allocating another one.
    java.lang.IllegalStateException: Invalid use of SingleClientConnManager: connection still allocated.
    Make sure to release the connection before allocating another one.
        at org.apache.http.impl.conn.SingleClientConnManager.getConnection(SingleClientConnManager.java:199)
        at org.apache.http.impl.conn.SingleClientConnManager$1.getConnection(SingleClientConnManager.java:173)
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:356)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
        at org.jfrog.build.client.PreemptiveHttpClient.execute(PreemptiveHttpClient.java:75)
        at org.jfrog.build.client.ArtifactoryBuildInfoClient.sendBuildInfo(ArtifactoryBuildInfoClient.java:209)
        at org.jfrog.hudson.BuildInfoDeployer.deploy(BuildInfoDeployer.java:58)
        at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:110)
        at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
        at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601)
        at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580)
        at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:598)
        at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
        at hudson.model.Run.run(Run.java:1276)
        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:124)
    Has anyone else encountered this problem ?

    1. Jun 17, 2010

      Yoav Landman says:

      This is a known issue that affects BuildInfo deployment - http://issues.jfrog.or...

      This is a known issue that affects BuildInfo deployment - http://issues.jfrog.org/jira/browse/HAP-40.
      The easiest workaround is to upgrade Artifactory (to 2.2.4 at time of writing).

  8. Oct 06, 2010

    Felipe Pacheco says:

    I installed the plugin, but when I tried to build a job (Build an Ivy project) t...

    I installed the plugin, but when I tried to build a job (Build an Ivy project) the following error is shown in the console output:

    "Building project with Ant Builder
    [com.tralix.pipeslave] $ cmd.exe /C '""C:\Eclipse Galileo\plugins\org.apache.ant_1.7.1.v20090120-1145\bin\ant.bat" -lib /root/.hudson/plugins/artifactory/WEB-INF/lib clean compile publish && exit %%ERRORLEVEL%%"'
    Error occurred during initialization of VM
    agent library failed to init: instrument
    Error opening zip file or JAR manifest missing : /root/.hudson/plugins/artifactory/WEB-INF/lib/aspectjweaver-1.6.9.jar
    [WARNINGS] Skipping publisher since build result is FAILURE"

    I checked the "/root/.hudson/plugins" and there is no artifactory folder

  9. Oct 12, 2010

    Andrew Dunn says:

    Hi, I'm using the artifactory plugin with ivy. When I create my jar file with i...

    Hi,

    I'm using the artifactory plugin with ivy. When I create my jar file with ivy it generates a file something like myjar_1.2.3.4.jar with a corresponding ivy file (ivy_1.2.3.4.xml), however when this is uploaded to artifactory using this plugin the jar and ivy files have had their names changed. the jar file is now called myjar_1-1.2.3.4.jar (it's got an extra '1-' before the version number) and the ivy file is now ivy-1.2.3.4.xml. Why does this happen shouldn't it be using the original ivy xml and jar file names?

  10. Oct 28, 2010

    Davide Cavestro says:

    Hi, I am using the artifactory plugin in a free-style project that uses a gradle...

    Hi, I am using the artifactory plugin in a free-style project that uses a gradle script (for a grails project), but as soon as I enable the Gradle-Artifactory Integration the build fails complaining "module not found: #build-info-extractor-gradle;1.0-SNAPSHOT" and similar things.

    I'm using:
    Hudson Artifactory Plugin 1.3.2
    Hudson ver. 1.381
    Artifactory 2.2.5 (rev. 11524)

    I noticed that in the <HUDSON ARTIFACTORY PLUGIN>/WEB-INF/lib/ folder there is a file named build-info-extractor-gradle-1.0.2.jar and others for the missing libraries. Is it my fault or a version compatibility issue?

    More specifically I get the following error:

    ...
    18:26:56 :: problems summary ::
    18:26:56 :::: WARNINGS
    18:26:56 module not found: #build-info-extractor-gradle;1.0-SNAPSHOT
    18:26:56
    18:26:56 ==== clientModule: tried
    18:26:56
    18:26:56 ==== da8075fa3c454f7d75c49fa4d734884c: tried
    18:26:56
    18:26:56 – artifact #build-info-extractor-gradle;1.0-SNAPSHOT!build-info-extractor-gradle.jar:
    18:26:56
    18:26:56 /mnt/workspace/plugins/artifactory/WEB-INF/lib/build-info-extractor-gradle-1.0-SNAPSHOT.jar
    18:26:56
    18:26:56 module not found: commons-logging#commons-logging;1.1.1
    18:26:56
    18:26:56 ==== clientModule: tried
    18:26:56
    18:26:56 ==== da8075fa3c454f7d75c49fa4d734884c: tried
    18:26:56
    18:26:56 – artifact commons-logging#commons-logging;1.1.1!commons-logging.jar:
    18:26:56
    18:26:56 /mnt/workspace/plugins/artifactory/WEB-INF/lib/commons-logging-1.1.1.jar
    18:26:56
    18:26:56 module not found: com.google.code.findbugs#jsr305;1.3.9
    18:26:56
    18:26:56 ==== clientModule: tried
    18:26:56
    18:26:56 ==== da8075fa3c454f7d75c49fa4d734884c: tried
    18:26:56
    18:26:56 – artifact com.google.code.findbugs#jsr305;1.3.9!jsr305.jar:
    18:26:56
    18:26:56 /mnt/workspace/plugins/artifactory/WEB-INF/lib/jsr305-1.3.9.jar
    18:26:56
    18:26:56 module not found: org.apache.httpcomponents#httpclient;4.0.1
    18:26:56
    18:26:56 ==== clientModule: tried
    18:26:56
    18:26:56 ==== da8075fa3c454f7d75c49fa4d734884c: tried
    18:26:56
    18:26:56 – artifact org.apache.httpcomponents#httpclient;4.0.1!httpclient.jar:
    18:26:56
    18:26:56 /mnt/workspace/plugins/artifactory/WEB-INF/lib/httpclient-4.0.1.jar
    18:26:56
    18:26:56 ::::::::::::::::::::::::::::::::::::::::::::::
    18:26:56
    18:26:56 :: UNRESOLVED DEPENDENCIES ::
    18:26:56
    18:26:56 ::::::::::::::::::::::::::::::::::::::::::::::
    18:26:56
    18:26:56 :: #build-info-extractor-gradle;1.0-SNAPSHOT: not found
    18:26:56
    18:26:56 :: commons-logging#commons-logging;1.1.1: not found
    18:26:56
    18:26:56 :: com.google.code.findbugs#jsr305;1.3.9: not found
    18:26:56
    18:26:56 :: org.apache.httpcomponents#httpclient;4.0.1: not found
    18:26:56
    18:26:56 ::::::::::::::::::::::::::::::::::::::::::::::
    18:26:56
    18:26:56
    18:26:56
    18:26:56 FAILURE: Build failed with an exception.
    18:26:56
    18:26:56 * What went wrong:
    18:26:56 Could not resolve all dependencies for configuration 'classpath':
    18:26:56 - unresolved dependency: #build-info-extractor-gradle;1.0-SNAPSHOT: not found
    18:26:56 - unresolved dependency: commons-logging#commons-logging;1.1.1: not found
    18:26:56 - unresolved dependency: com.google.code.findbugs#jsr305;1.3.9: not found
    18:26:56 - unresolved dependency: org.apache.httpcomponents#httpclient;4.0.1: not found
    18:26:56
    18:26:56 * Try:
    18:26:56 Run with -S option to get the full (very verbose) stacktrace.
    18:26:56
    18:26:56 * Exception is:
    18:26:56 org.gradle.api.artifacts.LocationAwareResolveException: Could not resolve all dependencies for configuration 'classpath':
    18:26:56 - unresolved dependency: #build-info-extractor-gradle;1.0-SNAPSHOT: not found
    18:26:56 - unresolved dependency: commons-logging#commons-logging;1.1.1: not found
    18:26:56 - unresolved dependency: com.google.code.findbugs#jsr305;1.3.9: not found
    18:26:56 - unresolved dependency: org.apache.httpcomponents#httpclient;4.0.1: not found
    18:26:56
    18:26:56 at org.gradle.api.internal.artifacts.ivyservice.DefaultIvyDependencyResolver$ResolvedConfigurationImpl.rethrowFailure(DefaultIvyDependencyResolver.java:101)
    18:26:56 at org.gradle.api.internal.artifacts.ivyservice.SelfResolvingDependencyResolver$1.rethrowFailure(SelfResolvingDependencyResolver.java:74)
    18:26:56 at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingIvyService$ErrorHandlingResolvedConfiguration.rethrowFailure(ErrorHandlingIvyService.java:82)
    18:26:56 at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationFileCollection.getFiles(DefaultConfiguration.java:495)
    18:26:56 at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.getFiles(DefaultConfiguration.java:169)
    18:26:56 at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration_Decorated.getFiles(Unknown Source)
    18:26:56 at org.gradle.api.internal.initialization.DefaultScriptHandler.updateClassPath(DefaultScriptHandler.java:36)
    18:26:56 at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:118)
    18:26:56 at org.gradle.configuration.DefaultInitScriptProcessor.process(DefaultInitScriptProcessor.java:37)
    18:26:56 at org.gradle.initialization.InitScriptHandler.executeScripts(InitScriptHandler.java:40)
    18:26:56 at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:125)
    18:26:56 at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:107)
    18:26:56 at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:75)
    18:26:56 at org.gradle.launcher.Main.execute(Main.java:93)
    18:26:56 at org.gradle.launcher.Main.main(Main.java:42)
    18:26:56 at org.gradle.launcher.GradleMain.main(GradleMain.java:49)
    18:26:56
    18:26:56 BUILD FAILED
    18:26:56
    18:26:56 Total time: 2.75 secs
    18:26:56 Finished: FAILURE

    My gradle script is the following (I replaced curly braces with angular ones cause I don't know this wiki syntax):

    buildscript <
    //    apply <
    //        apply from: 'http://myartifactoryserver:8081/artifactory/repo/org/jfrog/buildinfo/build-info-extractor-gradle/1.0.1/artifactoryplugin-1.0.1.gradle'
    //    >
        repositories <
            mavenCentral()
            mavenRepo urls: 'http://snapshots.repository.codehaus.org'
            mavenRepo urls: "http://repository.jboss.org/maven2/"
        >
        dependencies <
            classpath "org.grails:grails-gradle-plugin:1.0",
                      "org.grails:grails-bootstrap:1.3.4"
        >
    >
    apply plugin: "grails"
    repositories <
        mavenCentral()
        mavenRepo urls: ["http://repository.jboss.org/maven2/"]
    //    mavenRepo urls: "http://myartifactoryserver:8081/repo"
    >
    dependencies <
        compile "org.grails:grails-crud:1.3.4",
                "org.grails:grails-gorm:1.3.4",
                "org.springframework.security:spring-security-web:3.0.3.RELEASE",
                "org.hibernate:hibernate-tools:3.2.4.GA"
        runtime "org.slf4j:slf4j-log4j12:1.5.8"
    >

    Kind regards
    Davide

    UPDATE: after updating artifactory and hudson plugin the problem still persisted (even if mitigated), so I reported an issue against the jfrog JIRA.

  11. Jan 12, 2011

    Evgeny Goldin says:

    Hi, Still don't see v1.4.1 at http://repo2.maven.org/maven2/org/jvnet/hudson/pl...
    1. Jan 13, 2011

      Yossi Shaul says:

      Since the java.net migration, the deploy repository of artifacts is on http://ma...

      Since the java.net migration, the deploy repository of artifacts is on http://maven.hudson-labs.org:8081/content/repositories/releases/.
      You can find the new plugin version gere: http://maven.hudson-labs.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/artifactory/

      I don't know who is responsible to sync with the public maven repo.

      1. Jan 17, 2011

        Evgeny Goldin says:

        See it, thanks! It is also available at: http://updates.hudson-labs.org/download...