Specs - How to set custom plan branch for deployment project

[Pedro Sa da costa]

Using Java specs, how can I set a custom plan branch for a deployment project?

In the UI this option is under `/deploy/config/configureDeploymentProjectDetails` .

If this is not possible, is it possible in any other way to mass configure different deployment plans for the same build plan  being ran on different branches?

Best Regards,

Pedro

[Alexey Chystoprudov · Accepted solution]

Configure custom branch for deployment project through UI and then use menu item "View as Java Specs". It will generate Java code for current deployment project

[Pedro Sa da costa]

Hello Alexey,

Thanks for the tip, I can see now that the PlanIdentifier ID number changes for each branch. This was not oblivious from the API. 

Thank you for your help!

[Pedro Sa da costa]

After fiddling with this some more, this allows me to edit existing branches, but not to create new ones since I'm missing a BambooOid. Can this Id be retrieved somehow (using the API, or the GUI) from an existing build branch and not an existing deployment plan?

[Alexey Chystoprudov]

It's enough to use PlanIdentifier without oid

final Deployment rootObject = new Deployment(new PlanIdentifier("COM", "PLAN10")), "Test")

[Pedro Sa da costa]

Unfortunately that does not work for me when creating a new deployment:

    val deploymentName = "Tomcat Alpha deployment ${env.name.toUpperCase()}"
    val planIdentifier = PlanIdentifier(Vars.PROJECT_KEY, env.bambooPlanId)
    Deployment(planIdentifier, deploymentName)


// error
//
// Can't find deployment project by oid(null) or name(Tomcat Alpha deployment TEST)

Vars.PROJECT_KEY,  and env.bambooPlanId match the IDs i can see in the bamboo plan generated java specs if I create it manually.

[Alexey Chystoprudov]

This error message is from deployment permissions import.

Are you sure it's related to plan branches selection from topic header?

[Pedro Sa da costa]

You are correct! 

The problem was indeed from the permissions import. I was doing them before publishing the specs, which would cause an error when creating , but not when updating an existing plan.

Thank you for your help!