Bamboo: artifact naming convention limitation

[Mark de Bont]

When defining artifacts, where the name containing '.' and '?', it appears that Bamboo can not find the store the artifact itself.

Example:

When creating an artifact with the name "Tests-FW6.??-s2l-release.log" (without quotes) the job fails to archive the artifacts that are actually defined (*.log or something similar).

Is this a bug or a feature?

[Alexey Chystoprudov · Accepted solution]

@Tim Crall was right in his comment from June 01, you should not use special characters at artifact definition name. Created an issue to provide more useful error message https://jira.atlassian.com/browse/BAM-17633

[Mark de Bont]

Thanks for checking out, and voted! :wink:

[Alexey Chystoprudov]

Hello @Mark de Bont,

Tried to reproduce your issue at Bamboo 5.12.1

Created plan with script task:

echo "hello world" > Tests-FW6.00-s2l-release.log
echo "hello world" > Tests-FW6.01-s2l-release.log
echo "hello world" > Tests-FW6.100-s2l-release.log

Defined artifacts:

Screen Shot 2016-06-01 at 12.13.09.png

Execute build and received 2 files in artifact 

Screen Shot 2016-06-01 at 12.14.13.png

Does it looks different from your configuration?

[Mark de Bont]

Hi @Alexey Chystoprudov [Atlassian]

I'am using something similar

image2016-6-1 13:28:15.png

and then get the following result:

d:\gitb\l\26017793\SAN-PAT-JOB1>echo "hello world"  1>Tests-FW6.00-s2l-release.log

d:\gitb\l\26017793\SAN-PAT-JOB1>echo "hello world"  1>Tests-FW6.01-s2l-release.log

d:\gitb\l\26017793\SAN-PAT-JOB1>echo "hello world"  1>Tests-FW6.100-s2l-release.log

Unable to publish artifact [Tests-FW6.??-s2l-release.log]:

using Bamboo 5.12.1

[Tim Crall]

I'd recommend not using a question mark in the artifact name.  That seems like bad practice in any event.

[Alexey Chystoprudov]

it's pattern to copy artifacts, not part of file name