- Attachments:13
- Added by Yossi Shaul, last edited by Eli Givoni on Feb 05, 2015 (view change)
Hudson
Home
Downloads
Dev Mailing List
User Forum
IRC
Browse Sources
Report Bug
Documents
Getting Started
Using Hudson
Developing Plugin
Plugins
SCMs
Triggers
Build Tools
Build Wrappers
Notifiers
Reporters
Slave Launchers and Controllers
Uploaders
Other Post-build Actions
Ext. Site Integration
UI Plugins
Page Decorators
Authentication and User Management
Cluster Management and Distributed Build
CLI Extensions
Maven
Misc
Others
Container-specific Notes
Site Map
|
Plugin Information
This plugin allows deploying Maven 2, Maven 3, Ivy and Gradle artifacts and build info to the Artifactory artifacts manager.
IntroductionThe 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. RequirementsThis plugin requires Artifactory 2.2.3 or later and Hudson 1.358 or later. 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). 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 BuildsOnce 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.
Configuring Gradle BuildsYou 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 BuildsBy 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.
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 ControlYou use the Artifactory Pro License Control feature to discover and handle third party dependency licensing issues as part of the build. Watch the ScreencastTo see the Hudson Artifactory Integration in action you can watch the following screencast. Changelog3.1.0 (5 Feb 2015)
1.4.2 (27 Jan 2011)
1.4.1 (10 Jan 2011)
1.4.0 (09 Jan 2011)
1.3.6 (21 Nov 2010)
1.3.5 (7 Nov 2010)
1.3.4 (28 Oct 2010)
1.3.3 (21 Oct 2010)
1.3.2 (19 Oct 2010)
1.3.1 (19 Sep 2010)
1.3.0 (26 Aug 2010)
1.2.0 (26 Jul 2010)
1.1.0 (09 Jun 2010)
1.0.7 (04 Mar 2010)
1.0.6 (16 Feb 2010)
1.0.5 (22 Jan 2010)
1.0.4 (15 Jan 2010)
1.0.3 (07 Jan 2010)
1.0.2 (22 Dec 2009)
1.0.1 (16 Dec 2009)
1.0.0 (14 Dec 2009)
|
Labels:
Enter labels to add to this page: Looking for a label? Just start typing.
|
Comments (22)
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:
Did I miss anything? (Hudson 1.337; Artifactory 2.1.2; Plugin 1.0.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 installat