Hello, I'm with the team that caused this particular improvement request to be created. Our desired use case is as follows:
(1) When I check some source files into Perforce, Perforce fires a trigger script that starts a build on Bamboo.
(2) Bamboo runs a build plan that syncs the Perforce depot, checks out some files (executables we're about to build), and runs a make. These steps (other than the sync) are done via Windows batch files set up as Bamboo command tasks.
(3) After the build is done, the last step of the Bamboo build plan runs a batch file that does a "p4 submit" to check those newly built executables into the depot. (Checking into P4 is how we are currently distributing executables to our team.)
The issue, as mentioned in the request description above, is that the "p4 submit" step triggers another build because Bamboo detects it as a change even though it is not being triggered by the P4/Bamboo trigger.
May I request, with specific self-interest, that your team have a closer look at implementing this "opt-out" feature, please? Thanks! 
- Chuck Woo
- Sony Interactive Entertainment
Suggestion
BAM-20136 Constant build loop when use VcsCommit task
Hello, I'm with the team that caused this particular improvement request to be created. Our desired use case is as follows:
(1) When I check some source files into Perforce, Perforce fires a trigger script that starts a build on Bamboo.
(2) Bamboo runs a build plan that syncs the Perforce depot, checks out some files (executables we're about to build), and runs a make. These steps (other than the sync) are done via Windows batch files set up as Bamboo command tasks.
(3) After the build is done, the last step of the Bamboo build plan runs a batch file that does a "p4 submit" to check those newly built executables into the depot. (Checking into P4 is how we are currently distributing executables to our team.)
The issue, as mentioned in the request description above, is that the "p4 submit" step triggers another build because Bamboo detects it as a change even though it is not being triggered by the P4/Bamboo trigger.
May I request, with specific self-interest, that your team have a closer look at implementing this "opt-out" feature, please? Thanks!