Need troublshooting help for failed build trigger.

[Noah Zucker]

We use build branches to run cucumber integration tests in our different environments (qa, prod).

Using the build trigger, it failed. Here is the log output:

command 04-May-2017 11:51:43    Substituting variable: ${bamboo.target_deploy_environment} with qa
simple  04-May-2017 11:51:43    Starting task 'Trigger Integration Test' of type 'com.valens.bamboo.build.bamboo-build-task:chainBuildTask'
simple  04-May-2017 11:51:43    Starting build: NV-ANCUKE
simple  04-May-2017 11:51:43    prod
simple  04-May-2017 11:51:43    qa
simple  04-May-2017 11:51:43    Finished task 'Trigger Integration Test' with result: Failed

How can I troubleshoot this? The log output is minimal.

Screenshot of the configuration attached.

[Hutuleac Iulius]

if (planResultKey != null) { return TaskResultBuilder.newBuilder(taskContext).success().build(); } else { return TaskResultBuilder.newBuilder(taskContext).failed().build(); }

it says it didnt receive a result key from bamboo. Can you check if the subsequent build is actually triggering ?

[Noah Zucker]

Yes, the problem was that the target build plan did not have a branch matching the configured one.

After I set up a branch, it worked.

However, I think it is also failing if the number of concurrent builds is at a maximum. Is there a way to get around this and have it queue a build anyway? I suspect not.

[Hutuleac Iulius]

let keep an eye on the concurrent builds thingy. if you are right maybe we can do something else like retry count or something.