The folder to download the package to. The path can include environment variables in the format ${VAR} or $VAR.

If a full pathname is not supplied then the downloaded package 'should' end up in the workspace, but this is not guaranteed. If you wish the package to be placed in the workspace the it is best to use the Jenkins variable ${WORKSPACE}

See the list of available environment variables.

The feed in ProGet to upload the package to

The package you wish to upload your package to.

A string of no more than fifty characters:

• numbers (0-9)
• upper and lower-case letters (a-Z)
• dashes (-)
• periods (.)
• forward-slashes (/)
• and underscores (_)
• may not start or end with a forward-slash

e.g. an/example/group

The package you wish to upload your package to.

A string of no more than fifty characters:

• numbers (0-9)
• upper and lower-case letters (a-Z)
• dashes (-)
• periods (.)
• and underscores (_)

e.g. mypackage

A string representing a Semantic Version; this plug-in will not do any validation that the version is correct, however ProGet will return an error and the task will fail if the version number is not correctly formatted.

You can use wildcards like 'module/dist/**/*.zip'. See [the includes attribute of Ant fileset](http://ant.apache.org/manual/Types/fileset.html) for the exact format.

• Multiple patterns can be specified by placing a comma (,) between them
• The base directory is the workspace. You can only archive files that are located in your workspace
• Will fail the build if no files are found

Removing Unwanted Folders
Top level folders can be excluded from the package using a custom addition to the Ant fileset - wrapping unwanted folder names in square brackets ([ ]):

• filter must start with '['
• wildcards are not supported
• filter can span a several folders
• invalid filters are ignored
• can be used with multiple filesets

Examples:

• "[build]/sample/one.txt" would add the folder and file "sample/one.txt" to the package
• "[build/sample]/two.txt" would add the file "one.txt" to the package
• "build/[sample]/three.txt" would be ignored
• "[**]/four.txt" would be ignored
• "[one]/one.txt, [two]/two.txt" would add one.txt and two.txt to the package

Artifact archiver uses Ant org.apache.tools.ant.DirectoryScanner which by default is case sensitive. For instance, if the job produces *.hpi files, pattern "**/*.HPI" will fail to find them.

This option can be used to disable case sensitivity. When it's unchecked, pattern "**/*.HPI" will match any *.hpi files, or pattern "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar.

An array of strings, each consisting of a package identification string; this string is formatted as follows:

• �group�:�package-name�
• �group�:�package-name�:�version�

When the version is not specified, the latest is used.

A string containing any number of charters; these will be formatted as Markdown in the ProGet UI

Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". A file that matches this mask will not be archived even if it matches the mask specified in 'files to package' section.

A string of an absolute url pointing to an image to be displayed in the ProGet UI (at both 64px and 128px); if package:// is used as the protocol, ProGet will search within the package and serve that image instead

Custom metadata in 'key = value' pairs, each key/value pair must be on it's own line so for more than one entry you will need to expand the entry field. Each key must be unique. Each value must be no more than 50 characters.

If you need to add additional metadata, it's strongly recommended that you prefix these properties with an underscore (_) on the off-chance that a property you add will exist in a future version of the specification.

An optional title for your package

A string of no more than fifty characters