@atripp 5.2.27 has fixed the issue. Thank you so much!

Hello; It's a problem with the database... there was probably some failed change script, a while ago. But beyond that diagnosing/troubleshooting isn't going to be trivial and not worth the time, especially since... Postgres has been deprecated in 5.2. It won't be available in 5.3. So, I would recommend to take the opportunity to first move to SQL Server (i.e. install a new instance w/ same version that uses SQL Server). You can use this guide to migrate feeds: https://inedo.com/support/kb/1168/proget-feed-migration Then, you can perform the upgrade to 5.2 on the new instance. You can migrate feed-by-feed.

Hi @Jonathan-Engstrom , Have you tried wrapping your PSEnsure inside of a with block to force everything to run as a specific Resource Credential? Example using a resource credential named AdAdminResourceCredentials: with credentials = AdAdminResourceCredentials { PSEnsure ( Key: RSHStuff, Value: True, Collect: >> $ErrorActionPreference = 'SilentlyContinue' $TargetOU = 'Users' $Value = (Get-ADComputer -Identity $env:COMPUTERNAME).DistinguishedName -match $TargetOU $CurrentValue = (Get-ADComputer -Identity $env:COMPUTERNAME).DistinguishedName ((($Value -eq $true) -and (($env:COMPUTERNAME) -match 'MyComputerName')) -or ($env:COMPUTERNAME -notmatch 'MyComputerName')) >>, Configure: >> $samAccountName = $ServerName $newOU = [adsi]"LDAP://$TargetOU" $comp= ([adsisearcher]"samaccountname=$($ServerName)$").FindOne() Write-Host $comp.GetDirectoryEntry() >>, Debug: true, Verbose: true ); } Please note that my PowerShell in collect and configure is not 1 to 1 with yours, I would replace my PowerShell script with yours in those two properties. I also was talking with one of the solutions architects on a similar Otter execution question. He suggested that sometimes it is easier to figure out PowerShell issues by running PSExec under the local system account and attempting to run your PowerShell commands that way. It will sometimes show you more detailed errors than Otter. I would try running PSExec -s powershell, which will open up a PowerShell console as the local system account, and then typing in the lines of PowerShell you have had trouble with. Thanks, Rich

Error was related to how we had base install Windows Management Framework/Powershell installed. Updating to WMF/Powershell 4 resolved this error. Working through some mistakes in the scripting, but if I can get through it all without any more questions, I'll mark this post as answered.

Hello Rich It is very kind. This was exactly what looking for. Thanks a lot

The first thing that comes to mind is Integrated Windows Authentication; you often won't be able to authenticate unless your computer is on the domain. This is a limitatino/feature of Windows (i.e. it's by design to work this way). As a work-around, you can setup a second site that doesn't have IWS enabled, and point to the same folder on disk.

Thanks for tracking those down, I updated owner on them :)

Alright, fair enough. As I use Otter almost exclusively for checking for compliance, I will look forward to this. Nontrivial asks are always the best ones, right? :D

Hello Here is two exemple : one with Carbon module (http://get-carbon.org) One wit h xSmbshare (From Pwershll Gallery) I assumed you have install the module Ensure-DscResource ( ConfigurationKey: Identity, Name: Carbon_Permission, Module: Carbon, Properties: %(Path:$DFSFolder,Identity:$Mydomain\$MyGroup,Permission:FullControl) ); Ensure-DscResource ( Name: xSmbShare, Module: xSmbShare, Properties: %(Name:$ShareFolder,Path:$FoldertoShare,ReadAccess:$Mydomain\$MyGroup,FolderEnumerationMode:AccessBased,CachingMode:None) ); The Carbon example use as ConfigurationKey the property Identity while in the xSmbShare, the configuraitonKey is the default property (ie, Name) I hope to not make a mistake and it will be useful. Best Regards PhilippeC.

There haven't been any other feature requests for this, and we haven't researched the feasibility of doing it; however we did add Impersonation and Process Isolation, both which were in-demand features.

I don't know if it will be sufficient to provide access to only http://files.pythonhosted.org/ and https://pypi.org/ - it's very possible that the file hosting locations will change. This is the case on a lot of other package galleries, including NuGet.org. If ProGet can only download a portion of the files, then, there will probably be some strange errors. It's too difficult to generalize, so if you can provide us with a specific package and a specific reproduction situation, we'll be happy to try it. But, as the error says, ProGet does only support those wheel/source packages; the legacy "egg" format (10+ years old I think) is not supported. Your developers should be able to help convert it, and you can rehost the handful of "egg" packages as needed. As far as other errors you may see.... don't think of the "Diagnostic Center" as "checklist of things to fix", it's there to help diagnose a problem... and unless you have one reported by a user, it's probably fine. They can come from so many sources (including temporary network outages, users typing in wrong urls / passwords, etc).

@mcascone_8142 said in breaking forward slash inserted in downloadprogetpackage jenkins plugin: I opened a bug on Jenkins' JIRA: https://issues.jenkins-ci.org/browse/JENKINS-61299

Deleting the folders before backup is what is currently done. Thanks for your time.

Hi @mhull_0872, We just released the latest version of ProGet 5.2.26 on 2/28/2020 which includes the new Package Deployment API. You can learn more about the package deployment tracking feature here. We also have documentation on how to use the API endpoint here. Thanks, Rich

@atripp Thank you for getting back then. Sorry for the delay in response.

Hello; For this, we recommend just doing a Backup and Restore. Of course, the Detatch/Reattach is effectively the same thing, but don't forget the config. For the Git-based raft, the Database just contains the connection information to the Bitbucket repository... so it will just come over with the database.

Not a basic question, we're always working to make BuildMaster as easy to use as possible, so getting feedback on how to improve our docs and tutorials will be great :) If you haven't seen it already, we've recently updated our Azure DevOps Integration Documentation; there's a lot of content there, and we hope to continue to make it easier and include tutorials at some point. Basically though, I recommend you start with Create New Application > Azure DevOps CI/CD. That will create an application with the Azure DevOps CI/CD Template, and you can see how a "full CI/CD" would work. It should just build "out of the box", and use our publicly-available AzureDevOps repository. What your'e describing, it seems like just a small portion of that. Once you've got the manual process working, it's just a matter of creating a Git repository monitor. you can configure that to monitor the branches in your AzureDevOps repository. https://docs.inedo.com/docs/buildmaster/ci-cd/continuous-integration/build-triggers/repository-monitors

I've identified this and we'll get this fixed in the next maintenance release (shipping end of week, at the latest) as BM-3552

Thanks John. We have tried the FindPackagesById endpoint and this is completing in 75ms which is much more expected. We are going to continue with this API to see if we can get what we need from it.

Hello John I upgrade to version 6.2.5b8. The sync is working. I get all the servers, and roles, BUT I have seen a weird behaviour I had 3 env defined in Otter INTEGRATION DEVELOPPEMENT PRODUCTION and only two were sync in Buildmaster. DEVELOPPEMENT PRODUCTION The servers assigned to the missing environnement in Otter were assigned to the "none" environment. In OTTER, I assigned INTEGRATION as child of DEVELOPPEMENT, ran a sync and INTEGRATION appears in Buildmaster as child of DEVELOPPEMENT I removed the link to DEVELOPPEMENT, ran a new sync. Strange isn't it ? But now, every seems to works fine until the next bug Thanks Best regards PhilippeC.