...
The optional part starting with the =>
symbols and followed by the target directory name can be used to publish the files into the specified target directory. If the target directory is omitted, the files are published in the root of the build artifacts. You can use "." (dot) as a reference to the build checkout directory.
The target paths must not be absolute. Non-relative paths will produce errors during the build.
...
You can use build parameters in the artifacts specification. For example, use "mylib-%system.build.number%.zip
" to refer to a file with the build number in the name.
Examples:
Info |
---|
The same
|
You can use build parameters in the artifacts specification. For example, use "mylib-%system.build.number%.zip
" to refer to a file with the build number in the name.
Examples:
|
- install.zip — — publish file named named
install.zip
in in the build artifacts - dist — — publish the content of the the
dist
directory directory - target/*.jar — — publish all jar files in the the
target
directory directory - target/**/*.txt => docs — — publish all the txt files found in the the
target
directory directory and its subdirectories. The files will be available in the build artifacts under the thedocs
directory directory.
- reports => reports, distrib/idea*.zip — — publish reports directory as as
reports
and and files matching matchingidea*.zip
from the from thedistrib
directory directory into the artifacts root.
Anchor | ||||
---|---|---|---|---|
|
...