@tsteenbakkers The current configuration does not support Azure DevOps on premises, due to the hardcoding of the host in Get-AzdoAPIURL.ps1 ( $sb.Append('dev.azure.com') | Out-Null)
I was able to make minimal changes to have this working with On-premises AzDO, by adding the following changes:
-
Get-AzdoAPIURL.ps1 (starting with line 16):
`$profile = Get-AzdoAPIToolsProfile -profilename $profilename
$subdomain = $profile.Organization
$baseUrl = If ([string]::IsNullOrWhiteSpace($profile.collectionUrl)) {'dev.azure.com'} Else {$profile.collectionurl}
$sb = New-Object System.Text.StringBuilder
$sb.Append('https://') | Out-Null
if($area -eq 'Release'){
$sb.Append('vsrm.') | Out-Null
}
$sb.Append($baseUrl) | Out-Null`
-
Get-AzdoAPIURL.ps1 (adding a new variable for the collectionUrl):
$collectionUrl = Read-Host -prompt "Optional: Please provide the collection url if the instance of Azure DevOps is on premisses(tfs.yourlocalserver/tfs). The protocol is not needed"
@tsteenbakkers The current configuration does not support Azure DevOps on premises, due to the hardcoding of the host in Get-AzdoAPIURL.ps1 ( $sb.Append('dev.azure.com') | Out-Null)
I was able to make minimal changes to have this working with On-premises AzDO, by adding the following changes:
Get-AzdoAPIURL.ps1 (starting with line 16):
Get-AzdoAPIURL.ps1 (adding a new variable for the collectionUrl):
$collectionUrl = Read-Host -prompt "Optional: Please provide the collection url if the instance of Azure DevOps is on premisses(tfs.yourlocalserver/tfs). The protocol is not needed"