|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
The archive artifacts feature expects the build artifacts to reside in the workspace.
When searching for matching artifacts, it recursively scans the workspace and its subdirectories.
The actual work is delegated to the Ant DirectoryScanner, which will not break out of the parent directory (the workspace in our case).
See Jenkins help message:
See the @includes of Ant fileset for the exact format. The base directory is the workspace.
and Ant documentation:
In general, patterns are considered relative paths, relative to a task dependent base directory (the dir attribute in the case of <fileset>). Only files found below that base directory are considered. So while a pattern like ../foo.java is possible, it will not match anything when applied since the base directory's parent is never scanned for files.
To solve your particular problem, I would recommend you redirect your tool's output to a file in the job's workspace and configure archiving for that file.