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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,637
Community Members
 
Community Events
176
Community Groups

Visibility of pending commits/changes

Is there an easy way to view pending commits which have yet to be built.  I'm aware you can view commits for each run in the commits tab.  We have moved form TeamCity which showed all pending commits within the main dashboard.  This allowed us to easily see which builds were up to date and which had pending changes.  I currently have a manually triggered build and have non built changes but have no visibility of this through the UI.

1 answer

1 vote

Hi @Andrew Finch

The easiest way I know will still involve some manual steps. You would need to check the latest build revision and run a diff between that revision and the one in head. 
Bamboo does not have such feature and it seems that not a lot of users request that. I say that because we have an old feature request open for it and it does not have votes:

Usually, what we do in Bamboo, is configuring a build to be triggered when the changes arrive. Assuming we are ignoring changes in files and folders we don't want to consider (using git ignore and the exclude changesets feature), we would have builds only when necessary. You should not need to manually check when a build can run. Ideally, Bamboo should check the repositories for you and build them when necessary. 
Does it make sense to you?

Thanks Daniel, yes that all makes sense and was effectively what I was doing to compare changes.  The majority of our builds use triggers but some are built daily so still an issue. 

Hi @Andrew Finch

I'm not sure how can I help you further, maybe if you share why you need such a setting. More details would help me to check if we could do something else to help you with this.

Please add your vote and set yourself as a watcher in the feature request I shared. That seems to be the right feature to attack this need.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events