[Bug][Bamboo] Change the splicing of cicd_scopes.name and cicd_pipelines.name

[xiaomingzhang12]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Now cicd_scopes.name is spliced in the way of project + "space ” +“ -” + "space ”+ plan.

What do you expect to happen

cicd_scopes.name needs to be changed to project + "/" + plan, this kind of splicing logic.
Take the above screenshot as an example
The value of xm-1 - p1 needs to be changed to xm-1/p1.
The name in the table cicd_pipelines also needs to be changed to this splicing logic.

How to reproduce

See above

Anything else

No response

Version

main

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[d4x1]

hi @mintsweet
cicd_scopes.name comes from _tool_bamboo_plans.name, and _tool_bamboo_plans.name is set when uses choose bamboo plans inConfig UI via API HTTP PUT /connections/:connectionId/scopes, so I need your help to fix cicd_scopes.name.

cc @xiaomingzhang12

cicd_pipelines.name should be fixed in backend. @d4x1

[d4x1]

@Startrekzky @xiaomingzhang12
I found that plan's name form hlw-h3 - h2 is returned from bamboo's API, for example:

{
    "shortName": "h2",
    "shortKey": "H2",
    "type": "chain",
    "enabled": true,
    "link":
    {
        "href": "http://18.232.129.138:8085/rest/api/latest/plan/HLWH3-H2",
        "rel": "self"
    },
    "key": "HLWH3-H2",
    "name": "hlw-h3 - h2",
    "planKey":
    {
        "key": "HLWH3-H2"
    }
}

"name": "hlw-h3 - h2" is the plan's official name.

Shall we update it with our custom splicing logic?

[xiaomingzhang12]

@Startrekzky @xiaomingzhang12 I found that plan's name form hlw-h3 - h2 is returned from bamboo's API, for example:

{
    "shortName": "h2",
    "shortKey": "H2",
    "type": "chain",
    "enabled": true,
    "link":
    {
        "href": "http://18.232.129.138:8085/rest/api/latest/plan/HLWH3-H2",
        "rel": "self"
    },
    "key": "HLWH3-H2",
    "name": "hlw-h3 - h2",
    "planKey":
    {
        "key": "HLWH3-H2"
    }
}

"name": "hlw-h3 - h2" is the plan's official name.

Shall we update it with our custom splicing logic?

In that case, I think it's better to use the format returned by the bamboo api itself.