Octopus extension versions
There have been four major versions of the Octopus Extension:
- Version 1.2.x - obsolete, but still usable for older versions of TFS and Azure DevOps
- Version 2.0.199 - for TFS 2015 Update 2, TFS 2015 Update 3, TFS 2015 Update 4, and TFS 2017 RTM
- Version 3 - download for TFS 2017 Update 1
- Current Version - the current, most recent version of the extension, for Azure DevOps
Extension compatibility with Azure DevOps/Team Foundation Server
The following table shows compatibility between versions of Azure DevOps, TFS, and the Octopus extension
|Azure DevOps/TFS Version / Extension Version||1.2.x||2.0.199||3||4 and 5|
|Azure DevOps||Supported||Not supported||Supported||Supported|
|TFS 2017 Update 2||Supported||See below||Supported||Supported|
|TFS 2017 Update 1||Supported||See below||Supported||Not supported|
|TFS 2017 RTM||Supported||Supported||Not supported||Not supported|
|TFS 2015 Updates 2,3,4||Supported||Supported||Not supported||Not supported|
TFS 2017 Update 1 is technically supported with version 2.0.199 of the extension, but we do not recommended it.
Any version older than TFS 2015 Update 2 is not supported by any extension version.
Build information compatibility
When passing build information to Octopus from Azure DevOps, you may encounter issues when trying to use the build link generated by the Azure DevOps extension.
Specifically, the build link may return a
404 (Not Found) error when viewed. The cause for the issue is believed to be the result of a change to the format of the build URL supported by Azure DevOps.
The Build information step in the Octopus Azure DevOps extension expects the build to be viewed using a URL like this:
However, affected TFS versions expect the build to be viewed using a different URL like this:
Since the Build information step was created after this change, the only workarounds are to either try to create a URL re-write rule in TFS to display the build using the new URL format, or to update the TFS version.
Need support? We're here to help.