[BAM-18048] Artifact with invalid characters cannot be published

Type: Bug
Resolution: Invalid
Priority: Low
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- da-special-characters

Symptom Severity:
Severity 3 - Minor
Bug Fix Policy:
View Atlassian Server bug fix policy

Summary

Bamboo is no longer able to handle artifacts whose filenames have an umlaut (¨). It fails to publish artifacts in this case. This is a regression of ~~BAM-17614~~.

Environment

We can replicate it in Bamboo 5.12.0-D20160518T090318 but we cannot replicate in 5.10-OD-15-001 (haven't tested in other versions), which shows this has changed.

Steps to Reproduce

Create a build plan in Bamboo with a single task: a script task
Add the following code to the task: echo Test > testumlaut_ü.test
- Notice that the last ‘u’ has an umlaut
Create an artifact definition that includes the generated file (tested with shared artifacts)
- A simply copy pattern like ‘*’ is enough
Run the plan

Expected Results

The build is successfully run and the ‘testumlaut_ü.test’ is added as an artifact in the build result.

Actual Results

Though the build is successful, it doesn’t contain any artifacts.
The build log shows this:

error	24-May-2016 15:04:55	Unable to publish artifact [Test]: 
simple	24-May-2016 15:04:55	The artifact hasn't been successfully published after 13.33 s

The Bamboo Server logs show this:

2016-05-26 22:29:57.397037500 2016-05-26 22:29:57,396 INFO [http-nio-6990-exec-4] [ArtifactServlet] Receiving Artifact [Test] for TEST-TEST-JOB1-2
2016-05-26 22:29:57.400482500 2016-05-26 22:29:57,399 ERROR [http-nio-6990-exec-4] [ArtifactServlet] Exception when storing the artifact
2016-05-26 22:29:57.400483500 java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: testumlaut_ü.test
2016-05-26 22:29:57.400483500 	at sun.nio.fs.UnixPath.encode(UnixPath.java:147)
2016-05-26 22:29:57.400483500 	at sun.nio.fs.UnixPath.<init>(UnixPath.java:71)
2016-05-26 22:29:57.400484500 	at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281)
2016-05-26 22:29:57.400484500 	at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53)
2016-05-26 22:29:57.400489500 	at com.atlassian.bamboo.utils.BambooFiles.resolvePathUnderParent(BambooFiles.java:170)
2016-05-26 22:29:57.400489500 	at com.atlassian.bamboo.v2.build.agent.messages.ArtifactStreams.deserialiseStreamToDir(ArtifactStreams.java:79)
2016-05-26 22:29:57.400490500 	at com.atlassian.bamboo.agent.messaging.ArtifactServlet.storeArtifact(ArtifactServlet.java:114)
2016-05-26 22:29:57.400490500 	at com.atlassian.bamboo.agent.messaging.ArtifactServlet.doPost(ArtifactServlet.java:100)
2016-05-26 22:29:57.400492500 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
2016-05-26 22:29:57.400492500 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
2016-05-26 22:29:57.400492500 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
2016-05-26 22:29:57.400495500 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
2016-05-26 22:29:57.400496500 	at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:39)

The agent logs show this:

2016-05-24 15:19:22,865 ERROR [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [BambooArtifactHttpTransport] Unexpected HTTP status code: HTTP/1.1 500 Internal Server Error
2016-05-24 15:19:22,865 INFO [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Handler com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler did not publish the artifact
2016-05-24 15:19:22,866 WARN [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Unable to publish artifact [test]:

Notes

This is the only invalid character found so far, but there may be others.

Workaround

Change tasks to generate file names without the ‘umlaut’.

is a regression of

BAM-17614 Artifacts with invalid characters, like umlauts, cannot be published

Closed

Monique Khairuliana (Inactive) made changes - 19/Aug/2019 2:01 AM

Workflow	Original: Bamboo Workflow 2016 v1 - Restricted [ 1626678 ]	New: JAC Bug Workflow v3 [ 3382466 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Owen made changes - 24/Oct/2018 5:33 AM

Symptom Severity

Original: Minor [ 14432 ]

New: Severity 3 - Minor [ 15832 ]

Oleksandr Tkachenko made changes - 06/Dec/2016 7:52 AM

Labels

New: da-special-characters

Vincent Chin (Inactive) made changes - 01/Dec/2016 1:22 PM

Link

New: This issue is a regression of ~~BAM-17614~~ [ ~~BAM-17614~~ ]

Przemek Bruski made changes - 29/Nov/2016 10:44 PM

Resolution		New: Invalid [ 6 ]
Status	Original: Needs Triage [ 10030 ]	New: Resolved [ 5 ]

Vincent Chin (Inactive) made changes - 29/Nov/2016 2:28 PM

Description

Original: h3. Summary

Bamboo is no longer able to handle artifacts whose filenames have an umlaut (¨). It fails to publish artifacts in this case.

h3. Environment
We can replicate it in Bamboo {{5.12.0-D20160518T090318}} but we cannot replicate in {{5.10-OD-15-001}} (haven't tested in other versions), which shows this has changed.

h3. Steps to Reproduce
# Create a build plan in Bamboo with a single task: a script task
# Add the following code to the task: {{echo Test > testumlaut_ü.test}}
#* Notice that the last ‘u’ has an umlaut
# Create an artifact definition that includes the generated file (tested with shared artifacts)
#* A simply copy pattern like ‘*’ is enough
# Run the plan

h3. Expected Results
The build is successfully run and the ‘testumlaut_ü.test’ is added as an artifact in the build result.

h3. Actual Results
Though the build is successful, it doesn’t contain any artifacts.
The build log shows this:
{noformat}
error 24-May-2016 15:04:55 Unable to publish artifact [Test]:
simple 24-May-2016 15:04:55 The artifact hasn't been successfully published after 13.33 s
{noformat}

The Bamboo Server logs show this:
{noformat}
2016-05-26 22:29:57.397037500 2016-05-26 22:29:57,396 INFO [http-nio-6990-exec-4] [ArtifactServlet] Receiving Artifact [Test] for TEST-TEST-JOB1-2
2016-05-26 22:29:57.400482500 2016-05-26 22:29:57,399 ERROR [http-nio-6990-exec-4] [ArtifactServlet] Exception when storing the artifact
2016-05-26 22:29:57.400483500 java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: testumlaut_ü.test
2016-05-26 22:29:57.400483500 at sun.nio.fs.UnixPath.encode(UnixPath.java:147)
2016-05-26 22:29:57.400483500 at sun.nio.fs.UnixPath.<init>(UnixPath.java:71)
2016-05-26 22:29:57.400484500 at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281)
2016-05-26 22:29:57.400484500 at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53)
2016-05-26 22:29:57.400489500 at com.atlassian.bamboo.utils.BambooFiles.resolvePathUnderParent(BambooFiles.java:170)
2016-05-26 22:29:57.400489500 at com.atlassian.bamboo.v2.build.agent.messages.ArtifactStreams.deserialiseStreamToDir(ArtifactStreams.java:79)
2016-05-26 22:29:57.400490500 at com.atlassian.bamboo.agent.messaging.ArtifactServlet.storeArtifact(ArtifactServlet.java:114)
2016-05-26 22:29:57.400490500 at com.atlassian.bamboo.agent.messaging.ArtifactServlet.doPost(ArtifactServlet.java:100)
2016-05-26 22:29:57.400492500 at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
2016-05-26 22:29:57.400492500 at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
2016-05-26 22:29:57.400492500 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
2016-05-26 22:29:57.400495500 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
2016-05-26 22:29:57.400496500 at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:39)
{noformat}

The agent logs show this:
{noformat}
2016-05-24 15:19:22,865 ERROR [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [BambooArtifactHttpTransport] Unexpected HTTP status code: HTTP/1.1 500 Internal Server Error
2016-05-24 15:19:22,865 INFO [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Handler com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler did not publish the artifact
2016-05-24 15:19:22,866 WARN [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Unable to publish artifact [test]:
{noformat}

h3. Notes
This is the only invalid character found so far, but there may be others.

h3.Workaround
Change tasks to generate file names without the ‘umlaut’.

New: h3. Summary

Bamboo is no longer able to handle artifacts whose filenames have an umlaut (¨). It fails to publish artifacts in this case. *This is a regression of ~~BAM-17614~~*.

h3. Environment
We can replicate it in Bamboo {{5.12.0-D20160518T090318}} but we cannot replicate in {{5.10-OD-15-001}} (haven't tested in other versions), which shows this has changed.

h3. Steps to Reproduce
# Create a build plan in Bamboo with a single task: a script task
# Add the following code to the task: {{echo Test > testumlaut_ü.test}}
#* Notice that the last ‘u’ has an umlaut
# Create an artifact definition that includes the generated file (tested with shared artifacts)
#* A simply copy pattern like ‘*’ is enough
# Run the plan

h3. Expected Results
The build is successfully run and the ‘testumlaut_ü.test’ is added as an artifact in the build result.

h3. Actual Results
Though the build is successful, it doesn’t contain any artifacts.
The build log shows this:
{noformat}
error 24-May-2016 15:04:55 Unable to publish artifact [Test]:
simple 24-May-2016 15:04:55 The artifact hasn't been successfully published after 13.33 s
{noformat}

The Bamboo Server logs show this:
{noformat}
2016-05-26 22:29:57.397037500 2016-05-26 22:29:57,396 INFO [http-nio-6990-exec-4] [ArtifactServlet] Receiving Artifact [Test] for TEST-TEST-JOB1-2
2016-05-26 22:29:57.400482500 2016-05-26 22:29:57,399 ERROR [http-nio-6990-exec-4] [ArtifactServlet] Exception when storing the artifact
2016-05-26 22:29:57.400483500 java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: testumlaut_ü.test
2016-05-26 22:29:57.400483500 at sun.nio.fs.UnixPath.encode(UnixPath.java:147)
2016-05-26 22:29:57.400483500 at sun.nio.fs.UnixPath.<init>(UnixPath.java:71)
2016-05-26 22:29:57.400484500 at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281)
2016-05-26 22:29:57.400484500 at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53)
2016-05-26 22:29:57.400489500 at com.atlassian.bamboo.utils.BambooFiles.resolvePathUnderParent(BambooFiles.java:170)
2016-05-26 22:29:57.400489500 at com.atlassian.bamboo.v2.build.agent.messages.ArtifactStreams.deserialiseStreamToDir(ArtifactStreams.java:79)
2016-05-26 22:29:57.400490500 at com.atlassian.bamboo.agent.messaging.ArtifactServlet.storeArtifact(ArtifactServlet.java:114)
2016-05-26 22:29:57.400490500 at com.atlassian.bamboo.agent.messaging.ArtifactServlet.doPost(ArtifactServlet.java:100)
2016-05-26 22:29:57.400492500 at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
2016-05-26 22:29:57.400492500 at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
2016-05-26 22:29:57.400492500 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
2016-05-26 22:29:57.400495500 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
2016-05-26 22:29:57.400496500 at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:39)
{noformat}

The agent logs show this:
{noformat}
2016-05-24 15:19:22,865 ERROR [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [BambooArtifactHttpTransport] Unexpected HTTP status code: HTTP/1.1 500 Internal Server Error
2016-05-24 15:19:22,865 INFO [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Handler com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler did not publish the artifact
2016-05-24 15:19:22,866 WARN [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Unable to publish artifact [test]:
{noformat}

h3. Notes
This is the only invalid character found so far, but there may be others.

h3.Workaround
Change tasks to generate file names without the ‘umlaut’.

Vincent Chin (Inactive) made changes - 29/Nov/2016 2:28 PM

Description

New: h3. Summary

Bamboo is no longer able to handle artifacts whose filenames have an umlaut (¨). It fails to publish artifacts in this case.

h3. Environment
We can replicate it in Bamboo {{5.12.0-D20160518T090318}} but we cannot replicate in {{5.10-OD-15-001}} (haven't tested in other versions), which shows this has changed.

h3. Steps to Reproduce
# Create a build plan in Bamboo with a single task: a script task
# Add the following code to the task: {{echo Test > testumlaut_ü.test}}
#* Notice that the last ‘u’ has an umlaut
# Create an artifact definition that includes the generated file (tested with shared artifacts)
#* A simply copy pattern like ‘*’ is enough
# Run the plan

h3. Expected Results
The build is successfully run and the ‘testumlaut_ü.test’ is added as an artifact in the build result.

h3. Actual Results
Though the build is successful, it doesn’t contain any artifacts.
The build log shows this:
{noformat}
error 24-May-2016 15:04:55 Unable to publish artifact [Test]:
simple 24-May-2016 15:04:55 The artifact hasn't been successfully published after 13.33 s
{noformat}

The Bamboo Server logs show this:
{noformat}
2016-05-26 22:29:57.397037500 2016-05-26 22:29:57,396 INFO [http-nio-6990-exec-4] [ArtifactServlet] Receiving Artifact [Test] for TEST-TEST-JOB1-2
2016-05-26 22:29:57.400482500 2016-05-26 22:29:57,399 ERROR [http-nio-6990-exec-4] [ArtifactServlet] Exception when storing the artifact
2016-05-26 22:29:57.400483500 java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: testumlaut_ü.test
2016-05-26 22:29:57.400483500 at sun.nio.fs.UnixPath.encode(UnixPath.java:147)
2016-05-26 22:29:57.400483500 at sun.nio.fs.UnixPath.<init>(UnixPath.java:71)
2016-05-26 22:29:57.400484500 at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281)
2016-05-26 22:29:57.400484500 at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53)
2016-05-26 22:29:57.400489500 at com.atlassian.bamboo.utils.BambooFiles.resolvePathUnderParent(BambooFiles.java:170)
2016-05-26 22:29:57.400489500 at com.atlassian.bamboo.v2.build.agent.messages.ArtifactStreams.deserialiseStreamToDir(ArtifactStreams.java:79)
2016-05-26 22:29:57.400490500 at com.atlassian.bamboo.agent.messaging.ArtifactServlet.storeArtifact(ArtifactServlet.java:114)
2016-05-26 22:29:57.400490500 at com.atlassian.bamboo.agent.messaging.ArtifactServlet.doPost(ArtifactServlet.java:100)
2016-05-26 22:29:57.400492500 at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
2016-05-26 22:29:57.400492500 at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
2016-05-26 22:29:57.400492500 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
2016-05-26 22:29:57.400495500 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
2016-05-26 22:29:57.400496500 at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:39)
{noformat}

The agent logs show this:
{noformat}
2016-05-24 15:19:22,865 ERROR [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [BambooArtifactHttpTransport] Unexpected HTTP status code: HTTP/1.1 500 Internal Server Error
2016-05-24 15:19:22,865 INFO [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Handler com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler did not publish the artifact
2016-05-24 15:19:22,866 WARN [0-BAM::Elastic Agent on i-72c963cf::Agent:pool-3-thread-1] [AbstractArtifactManager] Unable to publish artifact [test]:
{noformat}

h3. Notes
This is the only invalid character found so far, but there may be others.

h3.Workaround
Change tasks to generate file names without the ‘umlaut’.

Vincent Chin (Inactive) created issue - 29/Nov/2016 2:26 PM

Assignee:: Unassigned

Reporter:: Vincent Chin (Inactive)

Affected customers:: 1 This affects my team

Watchers:: 3 Start watching this issue

Created:: 29/Nov/2016 2:26 PM

Updated:: 19/Aug/2019 2:01 AM

Resolved:: 29/Nov/2016 10:44 PM

Details

Description

Summary

Environment

Steps to Reproduce

Expected Results

Actual Results

Notes

Workaround

Attachments

Issue Links

Forms

Activity

People

Dates