So you mean that Custom revision never sets any value. Only read.
So e.g. if there is a git tag with version x.y.z, and custom build does target that build, then a checkout of that commit is done.
If there is a custom build with custom version q.w.e and there is no version information related to it, then the build should fail(?)
So instead of implicitly running the latest revision when running a build manually, you can explicitly specify an older revision to (re)create a build artifact based on previous versions etc.:
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
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