tsteenbakkers
commented
3 years ago Hey Adrian,
Thanks for your e-mail. The published version does indeed only work with the SAAS version of Azure DevOps. I'm not if i stated that clearly in the documentation. I haven't been able to test the on premise version of the tool yet, because I don't have one. I was afraid that the API endpoints (not just the baseurl) were different for on premise. Azure DevOps is a weird MS product and it would surely not have surprised me if they would.
So thank you a lot for testing this and pointing this out to me. Does the rest of the tool work properly while using azure devops server (on premise)? if so would you be so kind to create a pull request of the mentioned changes so I can incorporate them into the tool and give you credit for it?
Regards,
Tobi
On Wed, Jun 30, 2021 at 6:39 PM Adrian Marian @.***> wrote:
@tsteenbakkers https://github.com/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"
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Continuous-Data/AzDoAPITools/issues/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDI5FT2W6H4ORDEE4OOIATTVNCEVANCNFSM47SWR7GQ .
-- Met vriendelijke groeten,
Tobi Steenbakkers about.me/tsteenbakkers [image: Tobi Steenbakkers on about.me] http://about.me/tsteenbakkers
hideintheclouds
@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"