Update Octo TFS to support spaces nicely

[robpearson]

Note: This summary has been substantially rewritten July 4 by @thedewi to reflect changes in direction and new features and fixes.

The current TFS plugin doesn't fully support spaces. This PR:

• Filters projects based on the selected space.
• Takes into account servers that do not support spaces.

Fixes #135. Fixes #136.

Because this turned into a significant branch, this PR addresses some other issues:

• Updates the ADO Marketplace docs and screenshots.
• Fixes the dashboard widget (fixes #142).
• Fixes push task not to silently drop non-matching patterns.
• Renames "Package Application for Octopus" task for better search, consistency.
• Filters tenant dropdowns by project.
• Passes --ignoreSslErrors through when ignore SSL checkbox is checked (fixes #146).
• Reports some CLI version incompatibilities in a friendlier way.

Notes

To support a richer UI, this package now includes v3 tasks for compatibility, and v4 tasks to better support new features like Spaces, richer dropdowns, etc.

Tests

Overall goal is to add the enhancements and not break anyone existing builds.

Broad Tests against Azure DevOps online.

Rob created broad tests hitting a mixture of servers:

Octopus 2018.x - No spaces Octopus 2019.1.x - Supports spaces but I removed the default space and didn't set a new one. Octopus 2019.2.x - Supports spaces fully and it has a default spaces numerous other ones.

Regression Tests

Rob's general approach to regression tests was to test against the following:

• Octopus 2018.x - No Spaces - Test against a server without spaces support. Legacy spaces field is left blank and it should function fine.
• Octopus 2019.x - No Default Space - Test against a server with the default space removed and no default space set.
• Octopus 2019.x - Default Space - Test against a server with a default space and leave the 'Space Name' field blank so it uses it.
• Octopus 2019.x - Uses Spaces - Test against a server with a default spaces and numerous other spaces. Enter a non-default space name.

This included build processes for each scenario that did the following:

• Pull source and build.
• Package using Octopus plugin.
• Push to Octopus using Octopus plugin.
• Create a Release w/ the Octopus plugin
• Deploy a release w/ the Octopus plugin (using the previously created release)
• Promote a release w/ the Octopus plugin (using the previously deployed release)

Builds were created as per the above and successfully deployed to Octopus, then upgraded to the latest plugin and re-tested. Then updated to opt-in to use Spaces fully using the new UI.

Regression tests against TFS 2017 Update 1

Regression tests against Azure Devops Server vLatest

[mudra-octopus]

Consider removal of checkbox Octopus Server has Spaces? for older versions that doesn’t support spaces. i.e. Octopus 2018.2.8. Not sure if we can detect Octopus Deploy server version somehow and control the UI checkbox display.

[mudra-octopus]

The Space tooltip text is The space name within Octopus. You can leave this blank to use the default space. We may not be able to leave space blank if we have selected Octopus Server has Spaces? option.

[mudra-octopus]

Spaces dropdown should be mandatory once Octopus Server has Spaces? checkbox is ticked for all tasks in newer Octopus Deploy versions. It is currently a bit inconsistent on different task pages.

[mudra-octopus]

Project dropdown will be empty when an Octopus Deploy server will be selected with no default space option selected and Create Release in Space option not selected.

Will it make easier for user to have a message saying Select appropriate space if applicable or something.

[mudra-octopus]

Create Release in Space is unselected and View YAML has DeploymentProgressInSpace: true. Which selection is DeploymentProgressInSpace is this referring to ?

[thedewi]

I have rewritten the summary (top) to reflect changes in direction.