skip to content »

Hudson error updating group repository metadata

Publishing to your local file cache repository is the best way to go (i.e. The plugin will intercept the publish events and will replay them against Artifactory according to the configuration.

hudson error updating group repository metadata-65hudson error updating group repository metadata-61

To help you get started, you can use gradle-example-ci-server as a sample project you can build from your Jenkins Gradle job.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.The plugin currently supports Maven 2, Maven 3, Gradle and Ivy-Ant builds.From the Jenkins System Configuration Page (Manage Jenkins - Configure System) we can configure the Artifactory Plugin details.The plugin is used in the same way as the other Freestyle builds, but under "Deploy artifacts to Artifactory" you will find a mandatory *Combination Matches *field where you can enter the specific matrix combinations to which the plugin will deploy the artifacts.

Here you can specify build combinations that you want to deploy through a Groovy expression that returns true or false.

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.

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.

When you specify a Groovy expression here, only the build combinations that result in true will be deployed to Artifactory.