How do I control the nesting and output type of artifacts?

Question

We generate artifacts in our pipeline, e.g.

artifacts:

          upload:

            - name: myproduct.msi

              type: shared

              paths:

                - product\bin\x64\Release\en-US\myproduct.msi

2 questions:

* Is there a way to have the artifact just be the MSI rather than a ZIP containing the MSI?
* How can we make it so the ZIP isn't nesting the MSI? Currently the ZIP contains the folder product, which has bin under it, which has x64 under it, etc until the MSI is finally 5 levels deep in a nested folder structure - can we instead make it just have the MSI at the top level?

Arkadiusz Wroblewski · Answer

Hello @Jan Martin

One small addition to Mihai's answer. 🙂

You can upload the MSI directly to Bitbucket Downloads using curl.exe on your Windows runner. No separate Linux step or pipe is needed.

This gives you the original MSI file without the artifact archive.

Atlassian has a working example here:

https://support.atlassian.com/bitbucket-cloud/kb/upload-files-and-trigger-pipelines-on-bitbucket-cloud-using-self-hosted-windows-runners/

Best,

Arek🤠🧙‍♂️

Mihai_LeanZero · Answer

The nesting first. Paths are relative to the clone directory and bitbucket keeps the folder structure, no documented option flattens it (depth is only search depth).

Copy the MSI to the clone root at the end of the build step and point paths at the copy:

script:
  - Copy-Item product\bin\x64\Release\en-US\myproduct.msi .
artifacts:
  upload:
    - name: myproduct.msi
      type: shared
      paths:
        - myproduct.msi

Not tested, that's from the docs. Copy-Item assumes a windows runner, and the new artifact types want runner 3.31.0+.

The ZIP? Can't confirm. The docs don't say if a single-file artifact still comes down zipped.

For a bare MSI to download, Bitbucket Downloads via the atlassian/bitbucket-upload-file pipe, FILENAME plus your account email and a scoped API token: https://support.atlassian.com/bitbucket-cloud/docs/deploy-build-artifacts-to-bitbucket-downloads/ Pipes aren't supported on windows runners though (no docker there, it's in the windows runner docs), so I'd put that in a second linux step picking up the shared artifact.