search

OctopusDeploy / OctoTFS

| Public | Octopus extensions for Azure DevOps, TFS, VSTS, and VSO
https://marketplace.visualstudio.com/items?itemName=octopusdeploy.octopus-deploy-build-release-tasks
Other
0 stars 42 forks source link

Require Channel selection so that dependent dropdowns work reliably #163

Closed thedewi closed 5 years ago

thedewi commented 5 years ago

The Environment dropdown depends on the Channel dropdown. Azure DevOps won't populate the Environment dropdown until a Channel selection is made. If the user leaves Channel blank, the Environment dropdown just stays broken, which is not a great user experience.

I think on balance, it's better to make this mandatory and get two more clicks from the user, than leave them with a broken Environment dropdown.

slewis74 commented 5 years ago

Actually, there might be an issue with making this a required field. What if the build on a branch? In some cases the build would just want to deploy to Dev, for example, and rely on the channel version rules during the create to work out which channel is the right one.

thedewi commented 5 years ago

Actually, there might be an issue with making this a required field. What if the build on a branch? In some cases the build would just want to deploy to Dev, for example, and rely on the channel version rules during the create to work out which channel is the right one.

Thanks, I hadn't thought of that. I'm inclined to abandon this then.

Our remaining options would seem to be: (1) Slightly over-populate the environment dropdown with all the project's environments, regardless of Channel selection, so that it still works in the case when no Channel was selected (2) Accept that the environment dropdown will be empty.