Artifactory Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID artifactory Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
2.2.1
Nov 03, 2013
1.521
git (version:1.1.14, optional)
ant (version:1.2, optional)
ivy (version:1.17, optional)
gradle (version:1.15, optional)
perforce (version:1.3.7, optional)
jira (version:1.29, optional)
subversion (version:1.43, optional)
maven-plugin (version:1.521)
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Yossi Shaul (id: yossis)
Usage Installations 2013-Apr 3133
2013-May 3301
2013-Jun 3402
2013-Jul 3501
2013-Aug 3514
2013-Sep 3598
2013-Oct 3745
2013-Nov 3671
2013-Dec 3668
2014-Jan 3963
2014-Feb 4053
2014-Mar 4271

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 Jenkins-provided JIRA.


TABLE OF CONTENTS

Introduction

The Jenkins Artifactory Plugin brings Artifactory's Build Integration support to Jenkins. 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.
The plugin uses the Artifactory REST API for build management that can be used by other clients as well.
To learn more about the Artifactory-side of the Jenkins Artifactory Plugin, please read the documentation on the JFrog wiki.

Requirements

This plugin requires Artifactory 2.2.3 or later and Jenkins 1.358 or later.
Release management and build isolation requires Artifactory 2.3.3 or later and Jenkins 1.400 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 Jenkins' system configuration page (Manage Jenkins -> 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 Jenkins Free-style Jobs
The Jenkins Artifactory plugin supports running Maven 3 builds from free-style jobs by using a Maven 3 build step + a build environment section for the Artifactory Maven 3 integration (artifact and build information deployment). For Maven 3 builds users are encouraged to configure the Artifactory integration using Jenkins' native Maven 2/3 build projects.

Configuring Gradle Builds

You can use the Jenkins Gradle Plugin (configured under a free-style job) in conjunction with the Jenkins 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 Jenkins Ivy Plugin together with the Jenkins Artifactory Plugin your Ivy builds will publish artifacts and build information to Artifactory whenever an ivy:publish task is executed.

Install the Jenkins Ivy Plugin
To use the Jenkins Artifactory Plugin with Ivy builds you need to install the Jenkins 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.

Configuring Generic (Freestyle) Builds

Generic build integration provides Build Info support for any build type. This allows custom builds, such as non-Java builds to:

  1. Publish any artifacts to Artifactory, together with custom properties metadata, and keep published artifacts associated with the Jenkins build.
  2. Resolve artifacts from Artifactory that are required by your build.
    The 'Published Artifacts' section lets you specify which artifact files produced by the build will be published to Artifactory.
    At the end of the build run, artifacts in the build's workspace directory will be selected according to the specified patterns and will be published to Artifactory.

    The 'Resolved Artifacts' section lets you specify which artifact files you wish to resolve from Artifactory.
    Before the build starts, Jenkins will download these artifacts from Artifactory so the build can use them as dependencies.

    Optionally, you can also map the target path of deployed/resolved artifacts.

Release Management with Staging and Promotion

The Artifactory plugin also supports release management for Maven and Gradle builds. Read detailed instructions here.

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.

JIRA Integration

The Jenkins plugin may be used in conjunction with the Jenkins JIRA plugin to record the build's affected issues, and include those issues in the Build Info descriptor inside Artifactory and as searchable properties on deployed artifacts.
To activate the JIRA integration, make sure that Jenkins is set with a valid JIRA site configuration and select the Enable JIRA Integration in the job configuration page:

Aggregating Issues from Previous Builds

It is possible to collect under a build deployed to Artifactory all JIRA issues affected by this build as well as previous builds. This allows you, for example, to see all issues between the previous release to the current build, and if the build is a new release build - to see all issues addresses in the new release.
To accumulate JIRA issues across builds, check the "Aggregate issues from previous builds" option and configure the last build status the aggregation should begin from. The default last status is "Released" (case insensitive), which means aggregation will begin from the first build after the last "Released" one.

Build Isolation

When executing the same chain of integration (snapshot) builds in parallel, a situation may arise in which downstream builds resolve snapshot dependencies which are not the original dependencies existing when the build was triggered.
This can happen when a root upstream build has run and triggered downstream builds that depend on its produced artifacts. Then the upstream has run again before the running downstream builds has finished, so these builds may resolve newly created upstream artifacts that are not meant for them, leading to conflicts.

Solution

The Jenkins plugin offers a new checkbox for its Maven/Gradle builds 'Enable isolated resolution for downstream builds' which plants a new 'build.root' property that is added to the resolution URL.
This property will then be read by the direct children of this build and implanting them in their resolution URLs respectively, thus guaranteeing that the parent artifact resolved is the one that was built prior to the build being run.

Maven

In order for Maven to use the above feature, the checkbox needs to be checked for the root build only, and make sure that all artifacts are being resolved from Artifactory by using the 'Resolve artifacts from Artifactory' feature. This will enforce Maven to use the resolution URL with Maven builds, alongside with the 'build.root' property as a matrix param in the resolution URL.

Gradle

Once the 'Enable isolated resolution for downstream builds' has been checked, the build.root property will be added to all existing resolvers.

Excluded artifacts and the BuildInfo


By default when providing exclude patterns for artifacts, they will not get deployed into Artifactory but they will get included in the final BuildInfo JSON.
By marking the "Filter excluded artifacts from build Info" the excluded artifacts will appear in a different section inside the BuildInfo and by this providing a clear understanding of the entire Build.
This is also crutial for the promotion procedure, since it scans your BuildInfo JSON and trying to promote all the artifacts there, it will fail when you excluded artifacts unless you mark this option.

Discarding Old Builds

The Jenkins project configuration lets you specify a policy for handling old builds.

You can delete old builds based on age or number as follows:

Days to keep builds The number of days that a build should be kept before it is deleted
Max # of builds to keep The maximum number of builds that should be kept. When a new build is created, the oldest one will be deleted

Once these parameters are defined, in the Post-build Actions section, you can specify that Artifactory should also discard old builds according to these settings as follows:

Discard old builds from Artifactory Configures Artifactory to discard old builds according to the Jenkins project settings above
Discard build artifacts Configures Artifactory to also discard the artifacts within the build

Watch the Screencast

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

Changelog

2.2.1 (11 Nov 2013)

  1. Fix for IllegalArgumentException in Deployment when no deployment is defined in Job (HAP-241)

2.2.0 (16 Oct 2013)

  1. Fix parent pom resolution issue (HAP-236) from Jenkins 1.521
  2. Add support for maven 3.1.X
  3. Option to ignore artifacts that are not deploy because of include/exclude patterns from the build info (HAP-444)
  4. Enable credentials configuration for repository listing per project (HAP-430)
  5. Bug fixes

2.1.8 (26 Aug 2013)

  1. Fix migration to Jenkins 1.528 (HAP-428)

2.1.7 (31 Jul 2013)

  1. Maven build failure during deployment (HAP-420)
  2. Bug fixes (HAP-406)

2.1.6 (24 Jun 2013)

  1. Fix plugin compatibility with Jenkins 1.519 (HAP-418)

2.1.5 (23 Apr 2013)

  1. Black duck integration - Automatic Black duck Code-Center integration for open source license governance and vulnerability control (HAP-394)
  2. Gradle 1.5 support for maven and ivy publishes - New 'artifactory-publish' plugin with fully supported for Ivy and Maven publications (GAP-138)
  3. Bug fixes (HAP-341, HAP-390, HAP-366, HAP-380)

2.1.4 (03 Feb 2013)

  1. Generic resolution interpolates environment variables (HAP-352)
  2. Broken link issues (HAP-362,HAP-371,HAP-360)
  3. Minor bug fixes

2.1.3 (14 Oct 2012)

  1. Support include/exclude patterns of captured environment variables (BI-143)
  2. Bug fixes (HAP-343,HAP-4,GAP-136)

2.1.2 (08 Aug 2012)

  1. Aggregating Jira issues from previous builds (HAP-305)
  2. Bug fixes and improvements in generic deploy (HAP-319, HAP-329)

2.1.1 (31 May 2012)

  1. NPE on Maven2 builds (HAP-316)

2.1.0 (24 May 2012)

  1. Support for cloudbees 'Folder plugin' (HAP-312,HAP-313)
  2. Minor bug fixes

2.0.9 (15 May 2012)

  1. Fix UI integration for Jenkins 1.463+ (HAP-307)
  2. Minor bug fixes

2.0.8 (09 May 2012)

  1. Integration with Jira plugin (HAP-297)
  2. Support build promotion for all build types (HAP-264)
  3. Ability to leverage custom user plugins for staging and promotion (HAP-271, HAP-272)

2.0.7 (20 Apr 2012)

  1. Generic artifact resolution (based on patterns or other builds output) to freestyle builds (HAP-292)
  2. Optimized deploy - when a binary with the same checksum as an uploaded artifact already exists in the Artifactory storage, a new local reference will be created instead of reuploading the same content
  3. Bug fixes

2.0.6 (19 Mar 2012)

  1. Support Perforce in release management (HAP-265)
  2. Generic artifacts deployment (HAP-153)
  3. Bug fixes

2.0.5 (08 Dec 2011)

  1. Compatible with Gradle 1.0-milestone-6
  2. Different Artifactory servers can be used for resolution and deployment (HAP-203)
  3. Using the new Jenkins user cause class to retrieve triggering user. Requires Jenkins 1.428 or above (HAP-254)
  4. Release management with Git work with the latest plugin. Requires Git plugin v1.1.13 or above (HAP-259, JENKINS-12025)
  5. Build-info exports an environment variable 'BUILDINFO_PROPFILE' with the location of the generated build info properties file

2.0.4 (15 Aug 2011)

  1. Compatible with Jenkins 1.424+ (HAP-223)
  2. Resolved Maven 3 deployments intermittently failing on remote nodes (HAP-220)
  3. Target repository for staged builds is now respected for Maven 3 builds (HAP-219)
  4. Remote builds no longer fail when "always check out a fresh copy" is used (HAP-224)

2.0.3 (26 Jul 2011)

  1. Support for Git Plugin v1.1.10+ (HAP-217)
  2. Native maven 3 jobs doesn't work if the Jenkins home path contains spaces (HAP-218)
  3. Wrong tag URL is used when changing scm element during staged build (HAP-215)

2.0.2 (07 Jul 2011)

  1. Support Jenkins version 1.417+ (HAP-211)

2.0.1 (19 May 2011)

  1. Maven deployment from remote slaves - artifact deployment for Maven builds will run directly from a remote slave when artifact archiving is turned off, saving valuable bandwidth and time normally consumed by copying artifacts back to master for archiving and publishing (requires Maven 3.0.2 and above)
  2. Staging of Maven builds now correctly fails if snapshot dependencies are used in POM files (HAP-183)
  3. All staging and promotion commit comments are now customizable (HAP-181)
  4. Fix for staged builds failing on remote slaves (HAP-189)

2.0.0 (4 May 2011)

  1. Release management with staging and promotion support
  2. Support for forcing artifact resolution in Maven 3 to go through Artifactory (HAP-144)
  3. Isolated resolution for snapshot build chains for Maven and Gradle
  4. Ability to attach custom properties to published artifacts (HAP-138)
  5. Improved Ant/Ivy integration
  6. Improved Gradle integration
  7. Support saving pinned builds (HAP-129, HAP-140)
  8. Option to delete deployed artifacts when synchronizing build retention (HAP-161)

1.4.3 (7 Apr 2011)

  1. Compatible to work with Jenkins 1.405 (HAP-159)

1.4.2 (27 Jan 2011)

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

1.4.1 (10 Jan 2011)

  1. Synchronize the build retention policy in Artifactory with Jenkins' 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 Jenkins 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 Jenkins Ivy Plugin)
  2. Supporting incremental builds (HAP-52)
  3. Testing connection to Artifactory in the main configuration page
  4. Update Jenkins 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 (issue #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
plugin-report plugin-report Delete
plugin-buildwrapper plugin-buildwrapper Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Dec 19, 2009

    ttrepper - 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.jenkins-ci.org/browse/JENKINS-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.jenkins-ci.org:8081/content/repositories/releases/.
      You can find the new plugin version gere: http://maven.jenkins-ci.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.jenkins-ci.org/download/...
  12. Jul 27, 2011

    fcamblor - says:

    Hi there, I just installed Artifactory plugin v1.4.4 on Jenkins 1.409.1, and it...

    Hi there,

    I just installed Artifactory plugin v1.4.4 on Jenkins 1.409.1, and it fails while publishing an artifact, during a gradle build, on artifactory 2.3.4.

    Stacktrace is the following :

    before stands a big byte array (corresponding to my jar maybe ?)
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "HTTP/1.1 405 Method Not Allowed[EOL]"
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "Date: Wed, 27 Jul 2011 10:37:18 GMT[EOL]"
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "Server: Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.5.1 mod_jk/1.2.25 mod_python/3.3.1 Python/2.5.2 PHP/5.2.4-2ubuntu5.14 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g mod_wsgi/2.0 mod_perl/2.0.3 Perl/v5.8.8[EOL]"
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "Allow: GET,HEAD,POST,OPTIONS,TRACE[EOL]"
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "Content-Length: 602[EOL]"
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "Keep-Alive: timeout=15, max=100[EOL]"
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "Connection: Keep-Alive[EOL]"
    12:37:18.961 [DEBUG] [org.apache.http.wire] << "Content-Type: text/html; charset=iso-8859-1[EOL]"
    12:37:18.962 [DEBUG] [org.apache.http.wire] << "[EOL]"
    12:37:18.962 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnection] Receiving response: HTTP/1.1 405 Method Not Allowed
    12:37:18.962 [DEBUG] [org.apache.http.headers] << HTTP/1.1 405 Method Not Allowed
    12:37:18.962 [DEBUG] [org.apache.http.headers] << Date: Wed, 27 Jul 2011 10:37:18 GMT
    12:37:18.962 [DEBUG] [org.apache.http.headers] << Server: Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.5.1 mod_jk/1.2.25 mod_python/3.3.1 Python/2.5.2 PHP/5.2.4-2ubuntu5.14 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g mod_wsgi/2.0 mod_perl/2.0.3 Perl/v5.8.8
    12:37:18.962 [DEBUG] [org.apache.http.headers] << Allow: GET,HEAD,POST,OPTIONS,TRACE
    12:37:18.962 [DEBUG] [org.apache.http.headers] << Content-Length: 602
    12:37:18.962 [DEBUG] [org.apache.http.headers] << Keep-Alive: timeout=15, max=100
    12:37:18.962 [DEBUG] [org.apache.http.headers] << Connection: Keep-Alive
    12:37:18.962 [DEBUG] [org.apache.http.headers] << Content-Type: text/html; charset=iso-8859-1
    12:37:18.981 [DEBUG] [org.apache.http.impl.client.DefaultRequestDirector] Connection can be kept alive for 15000 ms
    12:37:19.001 [DEBUG] [org.apache.http.wire] << "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">[\n]"
    12:37:19.005 [DEBUG] [org.apache.http.wire] << "<html><head>[\n]"
    12:37:19.006 [DEBUG] [org.apache.http.wire] << "<title>405 Method Not Allowed</title>[\n]"
    12:37:19.008 [DEBUG] [org.apache.http.wire] << "</head><body>[\n]"
    12:37:19.009 [DEBUG] [org.apache.http.wire] << "<h1>Method Not Allowed</h1>[\n]"
    12:37:19.012 [DEBUG] [org.apache.http.wire] << "<p>The requested method PUT is not allowed for the URL /libs-snapshot-local/foo/bar/baaz/jars/baaz-0.1-SNAPSHOT.jar;build.name=baaz;build.timestamp=1311763038072;build.number=69.</p>[\n]"
    12:37:19.013 [DEBUG] [org.apache.http.wire] << "<hr>[\n]"
    12:37:19.014 [DEBUG] [org.apache.http.wire] << "<address>Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.5.1 mod_jk/1.2.25 mod_python/3.3.1 Python/2.5.2 PHP/5.2.4-2ubuntu5.14 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g mod_wsgi/2.0 mod_perl/2.0.3 Perl/v5.8.8 Server at repo.mycorporate.com Port 80</address>[\n]"
    12:37:19.015 [DEBUG] [org.apache.http.wire] << "</body></html>[\n]"
    12:37:19.016 [DEBUG] [org.apache.http.impl.conn.SingleClientConnManager] Releasing connection org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter@99a6440
    12:37:19.018 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnection] Connection shut down
    12:37:19.021 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':buildInfo'
    12:37:19.032 [ERROR] [org.gradle.BuildExceptionReporter]
    12:37:19.048 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build failed with an exception.
    12:37:19.051 [ERROR] [org.gradle.BuildExceptionReporter]
    12:37:19.052 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:
    12:37:19.053 [ERROR] [org.gradle.BuildExceptionReporter] Execution failed for task ':buildInfo'.
    12:37:19.064 [ERROR] [org.gradle.BuildExceptionReporter] Cause: Failed to deploy file: HTTP response code: 405. HTTP response message: Method Not Allowed
    12:37:19.067 [ERROR] [org.gradle.BuildExceptionReporter]
    12:37:19.067 [ERROR] [org.gradle.BuildExceptionReporter] * Exception is:
    12:37:19.069 [ERROR] [org.gradle.BuildExceptionReporter] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':buildInfo'.
    12:37:19.070 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:71)
    12:37:19.071 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:48)
    12:37:19.072 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:34)
    12:37:19.073 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:55)
    12:37:19.074 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:57)
    12:37:19.077 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:41)
    12:37:19.078 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)
    12:37:19.079 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:52)
    12:37:19.080 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:42)
    12:37:19.083 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.AbstractTask.execute(AbstractTask.java:237)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.execution.DefaultTaskGraphExecuter.executeTask(DefaultTaskGraphExecuter.java:167)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.execution.DefaultTaskGraphExecuter.doExecute(DefaultTaskGraphExecuter.java:160)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.execution.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:78)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.execution.TaskNameResolvingBuildExecuter.execute(TaskNameResolvingBuildExecuter.java:113)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.execution.DelegatingBuildExecuter.execute(DelegatingBuildExecuter.java:54)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:158)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:112)
    12:37:19.084 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:80)
    12:37:19.085 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.RunBuildAction.execute(RunBuildAction.java:41)
    12:37:19.088 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.RunBuildAction.execute(RunBuildAction.java:27)
    12:37:19.089 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.ExceptionReportingAction.execute(ExceptionReportingAction.java:32)
    12:37:19.090 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.ExceptionReportingAction.execute(ExceptionReportingAction.java:21)
    12:37:19.093 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:219)
    12:37:19.094 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:203)
    12:37:19.095 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.Main.execute(Main.java:55)
    12:37:19.096 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.Main.main(Main.java:40)
    12:37:19.097 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.ProcessBootstrap.runNoExit(ProcessBootstrap.java:46)
    12:37:19.099 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.ProcessBootstrap.run(ProcessBootstrap.java:28)
    12:37:19.101 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.launcher.GradleMain.main(GradleMain.java:24)
    12:37:19.102 [ERROR] [org.gradle.BuildExceptionReporter] Caused by: java.io.IOException: Failed to deploy file: HTTP response code: 405. HTTP response message: Method Not Allowed
    12:37:19.104 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:468)
    12:37:19.104 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:388)
    12:37:19.105 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:287)
    12:37:19.108 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.jfrog.build.extractor.gradle.BuildInfoRecorderTask.deployArtifacts(BuildInfoRecorderTask.java:263)
    12:37:19.108 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.jfrog.build.extractor.gradle.BuildInfoRecorderTask.closeAndDeploy(BuildInfoRecorderTask.java:194)
    12:37:19.108 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.jfrog.build.extractor.gradle.BuildInfoRecorderTask.collectProjectBuildInfo(BuildInfoRecorderTask.java:132)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.BeanDynamicObject.invokeMethod(BeanDynamicObject.java:158)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:93)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.jfrog.build.extractor.gradle.BuildInfoRecorderTask_Decorated.invokeMethod(Unknown Source)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.util.ReflectionUtil.invoke(ReflectionUtil.groovy:23)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$2.execute(AnnotationProcessingTaskFactory.java:129)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$2.execute(AnnotationProcessingTaskFactory.java:127)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:63)
    12:37:19.109 [ERROR] [org.gradle.BuildExceptionReporter] 	... 28 more
    12:37:19.115 [ERROR] [org.gradle.BuildExceptionReporter]
    12:37:19.116 [LIFECYCLE] [org.gradle.BuildResultLogger]
    12:37:19.117 [LIFECYCLE] [org.gradle.BuildResultLogger] BUILD FAILED
    

    Any hint ?

  13. Oct 09, 2011

    Emilio S. do Carmo says:

    I've configured jenkins to deploy in artfactory using maven the same way it is h...

    I've configured jenkins to deploy in artfactory using maven the same way it is here. When I run the job, jenkins deploys the jar, but does not create an pom.xml file in artifactory in build folder. What is missing?

  14. Oct 27, 2011

    Giuliano Ribeiro says:

    When I active -T option on my maven build(to build in parallel) and check th...

    When I active -T option on my maven build(to build in parallel) and check the Artifactory plugin option: "Deploy artifacts to Artifactory" the build hangs in the inicial steps, show me this error message on the jenkins Console:

    mavenExecutionResult exceptions not empty
    message : Internal error: java.lang.NullPointerException
    cause : null
    Stack trace :
    org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
    at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
    at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
    at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: java.lang.NullPointerException
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.wereThereTestFailures(BuildInfoRecorder.java:459)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.isPublishArtifacts(BuildInfoRecorder.java:454)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.addArtifactsToCurrentModule(BuildInfoRecorder.java:419)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.addFilesToCurrentModule(BuildInfoRecorder.java:390)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.finalizeAndAddModule(BuildInfoRecorder.java:376)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.finalizeModule(BuildInfoRecorder.java:339)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.projectSucceeded(BuildInfoRecorder.java:156)
    at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:74)
    at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:91)
    ... 10 more
    message : Internal error: java.lang.NullPointerException
    cause : null
    Stack trace :
    org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
    at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
    at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
    at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: java.lang.NullPointerException
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.wereThereTestFailures(BuildInfoRecorder.java:459)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.isPublishArtifacts(BuildInfoRecorder.java:454)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.addArtifactsToCurrentModule(BuildInfoRecorder.java:419)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.addFilesToCurrentModule(BuildInfoRecorder.java:390)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.finalizeAndAddModule(BuildInfoRecorder.java:376)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.finalizeModule(BuildInfoRecorder.java:339)
    at org.jfrog.build.extractor.maven.BuildInfoRecorder.projectSucceeded(BuildInfoRecorder.java:156)
    at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:74)
    at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:91)
    ... 10 more

    There's any kind of issue using this combination?

    1. Nov 07, 2011

      Matthew Meyers says:

      Giuliano, I am getting the same stack with the -T option and deploy option c...

      Giuliano, I am getting the same stack with the -T option and deploy option checked. Just curious if you have you found any resolution?

      Thanks 

      1. Nov 07, 2011

        Giuliano Ribeiro says:

        No solution found yet ..... :(

        No solution found yet ..... :(

    2. Nov 10, 2011

      Yossi Shaul says:

      I opened an issue for this bug: https://issues.jfrog.org/jira/browse/MAP-33. It ...

      I opened an issue for this bug: https://issues.jfrog.org/jira/browse/MAP-33. It will be fixed in the next version of the plugin. Thanks for reporting.

  15. Nov 17, 2011

    Artem Karpenko says:

    Hello everybody, the part of documentation about configuring deployment for mav...

    Hello everybody,

    the part of documentation about configuring deployment for maven project is a little confusing. Instead of "post-build step" you need to look at "Post-build Actions" section (with checkboxes).

    The confusing part is that "Post Steps" section contains button "Add post-build step" with drop-down that contains "Artifactory plugin" item. Selecting it will add empty (draggable) block with "Artifactory plugin" title. Saving page after that will result in seeing stacktrace:

    javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jfrog.hudson.ArtifactoryBuilder from {"kind":"org.jfrog.hudson.ArtifactoryBuilder","stapler-class":"org.jfrog.hudson.ArtifactoryBuilder"}
    	org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:603)
    	org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
    	org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:234)
    	org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
    	org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
    	org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
    	org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
    	org.kohsuke.stapler.Stapler.service(Stapler.java:159)
    	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    	hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
    	hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
    	hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
    	hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
    	hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
    	hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
    	hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
    ...
    
  16. Nov 29, 2011

    Larry Edelstein says:

    It's my first try at using this plugin, but nothing's happening in the build I'v...

    It's my first try at using this plugin, but nothing's happening in the build I've configured to use it. 

    The build is successful, just as before. I've configured it to write to our own Artifactory installation, specifying our server's URL, the target repos, and an include pattern for artifacts. But nothing in my build output has changed. There are no messages on the Artifactory console indicating it was contacted. No errors or anything in the Jenkins output. 

    Any idea what I might have forgotten?

  17. Mar 21, 2012

    David Li says:

    I have Jenkins 1.451, Artifactory 2.5.1, plugin 2.0.6. I can see my Artifactory ...

    I have Jenkins 1.451, Artifactory 2.5.1, plugin 2.0.6. I can see my Artifactory thru the plugin. I'm trying to follow "Configuring Generic (Freestyle) Builds" section. But I don't have this Generic Integration option at all. Am I missing anything?

  18. May 02, 2012

    Nimrod Argov says:

    I've gotten the plugin to create the release artifacts and put them into Artifac...

    I've gotten the plugin to create the release artifacts and put them into Artifactory, but then it always reverts the poms and doesn't even try to create a tag.

    I would have understood if it was trying and failing, but it doesn't seem to even try to commit the tag and the next development version.

    Any ideas?

  19. Apr 16, 2013

    Ajith Thampi says:

    What is the best way to make sure Jenkins uses artifactory to store all its arti...

    What is the best way to make sure Jenkins uses artifactory to store all its artifacts.

    Ex. conditions is when there is need to promote a build. It would have been correct to have the option to collect the build from artifactory and continue with that build. 

    Currently the build needs is archived as artifact and only the latest build can be made available from jenkins. This kinda blots and doesn't make good use of artifactory which should ideally be taking of build archives

  20. Apr 23, 2013

    D Z says:

    When the Jenkins plugin communicates with Artifactory to create a build, what RE...

    When the Jenkins plugin communicates with Artifactory to create a build, what REST API does it use to create the build info json?

    The documentation doesn't mention any API that allows you to update this json, so how does it happen? http://wiki.jfrog.org/confluence/display/RTF/Artifactory%27s+REST+API#Artifactory'sRESTAPI-BUILDS

    1. Apr 29, 2013

      D Z says:

      http://wiki.jfrog.org/confluence/display/RTF30/Build+Integration >> ...

      http://wiki.jfrog.org/confluence/display/RTF30/Build+Integration

      >> It sends a BuildInfo data object to Artifactory via REST at the end of deployment. BuildInfois a structured JSON object containing all the data about the build environment, artifacts and dependencies, in a standard and open manner.

      Yes, but HOW? Which REST API does it use? :(

  21. May 24, 2013

    Vlad Beffa says:

    Do the Include/Exclude Patterns support substitution of Jenkins environment/job ...

    Do the Include/Exclude Patterns support substitution of Jenkins environment/job variables? I tried this in the include pattern:

    **/${version_to_deploy}/**

    But this doesn't seem to work. It excludes everything.

  22. Sep 07, 2013

    Timmy Leahy says:

    I have three maven multi-module projects that depend on one another and I've bee...

    I have three maven multi-module projects that depend on one another and I've been trying to get the SNAPSHOT triggering to work between them rather than manually setting the up and down stream jobs:

    Project A version 1.0-SNAPSHOT

    Project B version 0.9-SNAPSHOT (depends on Project A version 1.0-SNAPSHOT)

    Project C version 0.8-SNAPSHOT (depends on Project B version 0.9-SNAPSHOT)

    After some digging around on internets and stack overflows, I'd updated Artifactory to have unique snapshot versions along with the snapshotRepository's uniqueVersion element in POM's distributionManagement. 

    Then I was having some difficulty getting the "Build whenever a SNAPSHOT dependency is built" trigger to activate for all the projects.

    I could trigger a build manually or by an SCM change in Project B that would get picked up by Project C, but for some reason, with identical Jenkins job settings, not between Project A and Project B.

    Then I noticed that the dependency from Project B to Project A was not a module defined in the POM's dependencies node, but in pluings for the maven-dependency-plugin (the module being used is code generation tool wrapped up in a zip and then unpacked for running during the generate-sources phase).

    Once I updated the POM's dependencies node with the Project A module Jenkins was able to identify Project B as a downstream project.

    Hope this helps anyone who's running into this.

  23. Nov 19

    Facundo Mateo says:

    I have version 2.2.1 configured for  Jenkins 1.539. In the Jenkins general...

    I have version 2.2.1 configured for  Jenkins 1.539.

    In the Jenkins general configuration, I set the Artifactory url and the deployment user. When I click the "Test" button, the Artifactory version is correctly returned. So I guess the configuration is ok.

    Howerer, when i try to configure a maven3 proyect, the list of repositories is empty. I can access the repositories though the REST Artifactory api  from the browser and I have a positive response from the server.

    Jenkins logs don't show any error.

    Any idea what could be the problem?