Customizing bamboo artifacts

[Johnny Kauffman]

We have a couple plans that both produce deliverables that end up in the root directory: the build "dropbox" on our network. Each plan that drops deliverables into here does so with a unique build number. So, plan A might create a folder called "Version 5.6.7.88" and place certain build artifacts in there.

Currently I have this working as an extra task at the end of each plan that copies the deliverables. However, I would prefer to use the bamboo "artifacts" capabilities instead.

1. Is there any way to allow my plans to copy the artifacts to a network location? Can it be customized the way I indicated above?

2. Is there any way for me to also copy the build log into the destination directories?

[Bob Swift (personal)]

We use a different approach by leaving the artifacts in Bamboo until they are needed by another process. The other process then requests them as needed. The requesting process puts the artifacts where they are needed and processes them from there. We use https://studio.plugins.atlassian.com/wiki/display/BCLI getArtifact to make it easy to request the artifact. In most cases, we ensure we get the lastest results by using exectuteBuild --wait.

We also have nightly build that runs a script that uses getArtifact to publish the latest artifact on remote network drives so remote users can access the latest daily artifact without network delay.

[Przemek Bruski]

You can use Bamboo's artifact functionality only to display artifacts, not copy them to a network location. In your scenario, they will be available in two places.

Answering your questions:

1. No, the proper way is to use a finalising task, like you have done.

2. Only if it exists as a file in your build directory.