nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem with Artifact Download from Windows to Linux

David R. Cattley

I have a plan/job that runs on a WIndows OS based agent and produces a shared artifact comprise of multiple files.

On another plan/job that runs on a Linux based agent I use the Artifact Download task to copy these artifacts into the build.

The problem is that instead of the directory tree being recreated the Artifact Download task creates "files" in the root of the build folder that have literal backslash embedded.

It would seem that the notion of "path separator" is not conveyed properly via this mechanism.

Example:

The produced (on Windows) shared artifact might be: foo/bar/data.txt

The staged (on Linux) artifact ends up being a file named foo\bar\data.txt

This, of course, is complete nonsense.

Is there some option / trick that needs to be enable to make this work?

TIA

Dave Cattley

Accepted answers

All comments

Daniel Santos_157bm4

Hi David,

There was a bug in the past (reported for our cloud instances - In that time we had Bamboo cloud) which has the exact behavior you are describing now. This is the one: Artifact folders produced on Windows are being published as files.

I was trying to reproduce the same issue in a recent Bamboo version (6.7.2) and I was unable to reproduce it.

Could you share with us what is the Bamboo version affected?
Could you also share how the artifact definition is declared?

David R. Cattley

Version: 6.6.1

The artifact is defined with a pattern (like the following):

Location: <blank>

Pattern: **/foo/bar/*.*

David R. Cattley

[aside] I lament the demise of Bamboo Cloud ...

Daniel Santos_157bm4

[aside] I lament the demise of Bamboo Cloud ...

After some strategy analysis our company released that Bitbucket Pipelines would be a better fit for a Cloud offer and this is why Bamboo is only offered as self hosted instances.

Getting back to the artifact thing, I've tried to reproduce this issue also in Bamboo 6.6.1 using a remote agent on Windows 10 and consuming the artifact on a Linux agent with multiple artifact definitions based on your description but no luck yet.

I've opened a support request for you so we can investigate this further and get more details from your server that could not be shared in this channel. You should receive a confirmation email from our support website.

I would kingly ask you to share here the resolution you get from our support channel so other users that come to this thread will be able to take advantage of our work together and save their time.

Thank you!

David R. Cattley

1. Wait for Atlassian to fix it.

2. Use some other tool / container (e.g. ZIP, TAR, whatever) to pack the artifact files into a single object and unpack it on the destination.

David R. Cattley

Putting this into a script task after the Artifact Download task will "fixup" (move) the artifact files to the expected location(s) in the local file system.

#!/bin/bash
for _src in `find . -type f -regex '.*[\\]+.*'` ; do
 _dst="${_src//\\//}"
 mkdir -vp $(dirname $_dst)
 mv -v "$_src" "$_dst"
done

I am a shell script novice so YMMV but this seems to have done what I need it to do.

David R. Cattley

@Daniel Santos what ever became of this? Anything? Has it been fixed in some release since 6.9.1 ?

thx

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

artefact