-
Project by Deployment Group
- Configure Deployment Group Name on Project Properties.
- Do not use anything for Plugin Input for Deployment Group Name. i.e. workflow does not assign anything to Plugin Input for deployment group name.
- It is advisable to keep Project Name same as Deployment Group Name for clarity.
- This option works well with Release Snapshot and Pipeline based execution and helps with continue delivery.
- You will also be able to see reports very clearly by deployment group name as that is same as project name.
- Downside of this approach is that you will end up creating many projects and possibly inactivate them once not being used.
-
Ad-hoc Project to perform Build and Deploy using Input for Deployment Group name.
- Do not use anything for Deployment Group Name on Project Properties.
- Configure Workflow Input to be passed into Plugin Input for Deployment Group Name.
- This option works for Ad-hoc deployments, but it will not fit in Release and Pipelines.
- Reports will also not be very useful with this approach.
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Deployment Group Name |
| No | Use to pass in the name of the deployment group to migrate. Defaults to the project name, so consider creating a project per deployment group that you wish to migrate. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Deployment Group Name |
| No | Use to pass in the name of the deployment group to migrate. Overrides the project property of the same name. |