Properties are for Guiding, not for Restricting
When you define a property-set with 'strongly-typed' property values, those values are used to provide an intuitive, guiding UI for tagging and locating items.
The actual value does not force a strong relationship to the original property-set's predefined values. This is by design, to not slow-down common repository operations and for keeping artifacts management simple by allowing properties to change and evolve freely over time, without worrying about breaking older property rules.
Properties are therefore a helpful and non-restrictive feature.
Creating a Property Set
To create a new property set, go toAdmin | Artifactory | General | Property Setsand clickNew．
Add a Property Set Name, clickNewand add properties. The newly created property set will be available to use and add to a repository.
Assigning Property Sets to a Repository
To assign a property set to a repository which can then be selected from with the Artifact browser, go toAdministrationmodule |Repositoriesand select a repository.
In theAdvanced tab, select the property sets you would like to be available under this repository.
添加Property Sets to a Specific Repository
To add a property set to a specific repository, go toApplicationmodule |Artifactsand select a repository.
In theProperties tab, select the property sets you would like to add.
Attaching Properties via the UI
When selecting any item in the tree browser, you can view itsPropertiestab to view or edit the properties attached to the item.
You can edit the value of any property and clickSave．
Attaching and Reading Properties via REST API
Properties are a special form of metadata and are stored on items just like any metadata - in XML form.
In fact, you can view properties not only from theArtifacts:Propertiestab, but also from theArtifacts:Metadatatab, in which you can examine properties as they are stored in XML form. The properties XML is using thepropertiesroot tag and has a very simple format.
You can setset、检索updateandremoveproperties from repository items via REST API, as you would do with any other XML-based metadata.
