Local and Remote Repositories

Skip to end of metadata
Go to start of metadata
Table of Contents
Expand all   Collapse all

Overview

This section covers the controls that are common between local and remote repositories.

Snapshots and Releases Handling Policy

You can configure whether a local or remote repository handles snapshots and/or release artifacts.
The repository will reject deployments that are conflicting with this policy and will not participate in conflicting resolution requests.

Snapshot and release handling are currently supported for artifacts that follow the Maven naming conventions.
Support for flexible non-Maven snapshot and release identification will be introduced in the upcoming release of Artifactory.

Repository Blackout

It is possible, if desired for whatever reasons, to completely black-out a repository by marking its "Blacked Out" flag, making it effectively disabled. A blacked-out repository does not participate in any artifacts resolution and artifacts cannot be downloaded from it or deployed to it.

Suppressing POM Consistency Checks

By Default, Artifactory tries to keep your repositories healthy by refusing bad POMs that have wrong coordinates (path). If the information groupId:artifactId:version inside the POM does not match the deployed path, Artifactory will reject the deployment.
You can disable this behavior by selecting the "Suppress POM Consistency Checks" checkbox.
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

4 Comments

comments.show.hide

  1. Aug 01, 2009

    Joe Caporaletti

    I'm trying to interpret the meaning of the sentence "The repository will reject deployments that are conflicting with this policy and will not participate in conflicting resolution requests." under the Snapshots and Releases Handling Policy. First question for clarification: If both Handle Snapshots and Handle Releases are turned off, would all deployments fail? Second question: Is a conflicting resolution request one that conflicts because it is asking for a SNAPSHOT when Handle Snapshots is turned off? Or does it mean there is a conflict with another repository (e.g. more that one repository has the artifact?) The same question applies for the maining of a conflicting Release request.

    1. Aug 05, 2009

      Yoav Landman

      > If both Handle Snapshots and Handle Releases are turned off, would all deployments fail?
      Yes (sure, not a very useful combination...)

      > Is a conflicting resolution request one that conflicts because it is asking for a SNAPSHOT when Handle Snapshots is turned off?
      Yes

  2. Apr 04, 2011

    Carlton Brown

    This feature has always been a little unclear to me... 

    1:  What does "handle" mean in this context?   Does this mean "accept"?   Or does it mean trigger some other events after deployment?

    2:  What criterion qualifies a deployment as a snapshot vs. release?   For example, what specific piece of data in the pom.xml or ivy.xml or filename signals that a deployment is a release (or a snapshot)?  

    1. Apr 04, 2011

      Noam Y. Tenne

      1. "Handle" means "Accept"; that is, if the artifact is identified as a valid module, the repository will reject\accept accordingly. If the artifact cannot be resolved to a valid module then it will always be accepted (unless it doesn't comply to permissions, include\exclude patterns, etc.).

      2. I'll try to make my answer as clear as possible, but to fully understand please read the repository layouts user guide.
      The repository layouts define patterns that are the accepted arrangements of a path within a repository. Any path can be deployed to a repository, but for an artifact to be recognized as a module, it's deployment path must conform to the patterns that the hosting repository is configured with.
      The pattern helps artifactory extract the module information of an artifact based on it's path. This repository layout configuration also sets the criteria for which an artifact is considered a release or a snapshot\integration.