Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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.
  2. Ad-hoc Project to perform Build and Deploy using Input for Deployment Group name.
    1. Do not use anything for Deployment Group Name on Project Properties.
    2. Configure Workflow Input to be passed in to Plugin Input for Deployment Group Name.
    3. This option works for Ad-hoc deployments but it will not fit in Release and Pipelines.
    4. Same approach can be applied to Utility project as well but that will also not work well in Release and Pipelines, and Reports will also not be very useful with this approach.

Environment/Instance Properties

...