jfrog / teamcity-artifactory-plugin

TeamCity plugin that enables traceable build artifacts with Artifactory
https://www.jfrog.com/confluence/display/JFROG/TeamCity+Artifactory+Plug-in
Apache License 2.0
42 stars 47 forks source link

TeamCity builder custom build dependencies documentation is contradictory #25

Open chefhoobajoob opened 8 years ago

chefhoobajoob commented 8 years ago

The on-screen documentation for the builder Artifactory's custom dependencies configuration has this text:

New line or comma separated references to other build artifacts that this build should
use as dependencies. Each reference is specified in the format of: 
...
path_pattern - An Ant-like pattern of the dependencies path within the Artifactory
(may contain the * and the ? wildcards, including **). 
For example: repo-key:dir/*/bob/*.zip (** wilcards are not supported) 
...
build_number - A specific build run number. Can be LATEST to depend on the
latest build run, or LAST_RELEASE to depend on the latest build with a "release" status.
For example: repo-key:dir/**/bob/*.zip@myBuild#LATEST

It is not possible to tell from this documentation whether ** wildcards are supported in path_pattern, because it explicitly states in the definition of path_pattern that these wildcards are supported, then goes on in a later example to state that they are not supported, then goes on in yet another example to use them in the path_pattern. Are they allowed in some places but not others? Not at all? Anywhere? If not permitted anywhere, why do they appear in the examples?

My experience with the plugin is that it rejects the use of ** wildcards anywhere in path_pattern.

The documentation should be corrected to consistently indicate that these wildcards are not supported.