Change By: Ken Beal (19/Nov/14 6:06 PM)
Summary: Archive artifacts cannot start with "./", but "Parameters from properties file" can  (dot slash)
Description: We had a build job that passed info to another build job.  This file was not being archived, but I wanted to see its contents to determine where an issue had happened.  So I copied the line from the "Parameters from properties file" (in "Trigger parameterized build on other projects"), and pasted it in "Files to archive".

When I then ran a build, it failed with this somewhat amusing message:

--------------------------------------------------
Archiving artifacts
ERROR: No artifacts found that match the file pattern ".\depot\tokyo\upside\CI\AutoDeploy\data\ATF_data.txt". Configuration error?
ERROR: ‘.\depot\tokyo\upside\CI\AutoDeploy\data\ATF_data.txt’ doesn’t match anything, but ‘depot\tokyo\upside\CI\AutoDeploy\data\ATF_data.txt’ does. Perhaps that’s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
--------------------------------------------------

It looks like the way that it handles the leading ".\" may be different from how the Parameterized Trigger Plugin does.


Adding "dot slash" in summary and description, as it seems I cannot search for ".\" (I had tried "dot slash" but didn't see anything relevant, so if someone else does the same actions, they'll find this one).
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/d/optout.

Reply via email to