It's not possible to have another build with the same build number.
You can rerun a build if you'd like, but that would mean that the same repository state will be used (same commits, nothing new). If you run a new build (either manually or if it gets triggered) it's always assigned a new build number.
But why would you want to reuse the same build number (and thus erase the build information - logs, artifacts) in the first place? It's always better to create a new build, and if you think the old build is expired and no longer needed, you can delete it manually or configure build expiry feature to do it periodically/autmatically.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs