Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Tracking artifacts across plans

I'm attempting to configure a C++ project that uses several shared static libraries (Artifacts) to build a single executable. The configuration looks something like below:

Library 1-->   |

                      |  -> Final executable -> Deployment Project

Library 2 -->  |


The two libraries are shared between multiple plans so they're built and tested in their own plans then downloaded by the plan for the final executable.

What I'm searching for, is which builds did Libraries 1 and 2 come from to compose the final artifacts that are getting sent to the deployment project. This would allow me to know all the commits composing the final .exe.

I've been searching for how to do this for hours.

Many thanks!

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events