Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Multi-platform artifacts - can you subset what gets downloaded by platform?


If you have multiple platform specific build steps that produce artifacts for later steps, how do you configure the artifacts that get downloaded to a specific step to only those coming from a specific platform/step? Even in general, it seems you should be able to control what artifacts get downloaded either by name or step name or ??? .

2 answers

1 accepted

0 votes
Answer accepted
lliang2 Atlassian Team Jan 19, 2022

Hey @Bob Swift _Appfire_ 

I guess what you want is a generic feature that you can only download subset of artifacts in certain steps?

Unfortunately, we don't support it at the moment, I will let the team know about it for sure. In the meantime, I found that we already have a open ticket for it:

You can follow that ticket and upvote it.


Leo Liang

Thanks for the link. I think a generic solution would be best. I have determined it is pretty much impossible to have Linux and Windows builds in the same pipeline if they have artifacts. I have resorted to a linux only pipeline that kicks off the windows specific pipeline at the appropriate point. It makes it harder to visualize/understand the status in the pipeline list which could use some improvements.  

lliang2 Atlassian Team Jan 20, 2022

Hmm, I guess as walk around, you can generate the artifact in different folders base on the platform? i.e. for linux step, generate artifacts under "./linux/artifacts/**", and in windows, generate artifacts under "./windows/artifacts/*"

Then even though you still need to download all artifacts, you would at least able to seperate the artifacts you want to use for different platform?

Not really feasible with the size of our artifacts and number of steps. We are pretty much into multiple pipelines for that and other limitations related to parallelism and step dependencies.

If I understand correctly , In the below scrip I am using a build -wrapper to catch the c++ builds and downloading the build artifacts , and using in the next step.
    - step:
        name: "Build" 
            - cd projects/Application
            - build-wrapper-linux-x86-64 --out-dir build_wrapper_output_directory make -j clean all            
          - projects/Application/**    
      - step:
         name:  "Sonar"   
            -  cd projects/Application
            -  sonar-scanner- -X -Dsonar.projectBaseDir=${BITBUCKET_CLONE_DIR} -Dsonar.login=${SONAR_LOGIN} 

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you