It looks like this was caused by a packaging issue with installation; this impacts some upgrades and certain Linux-based querying from the web app (i.e. if you just save, and don't validate, it should work).. You can manually fix by going to the BuildMaster installation directory and: Delete the libssh2.dll file from the Web\bin directory Copy the Service\lib directory to the Web\bin directory (so Web\bin also contains the lib directory) We will of course get an updated installer built as well, but this should get things working for you until then.

It looks like the Legacy Plan Importer currently does not support the ExecutionStatusPredicate and ReleaseStatusPredicate, which is throwing the error; we will fix this in a maintenace release, but as a work-around you can delete the predicate before converting.

The error you shared was: An error occurred processing a PUT request to {url}: Invalid user name or password. A PUT request is what the NuGet client does to push packages to a feed. You'd want to look for a message related to GET or other requests. But, if you're seeing an unknown, then the problem is likely authentication related, but you'd have to look in the error log, it could be a bad url too... You can always try run fiddler, and attach ProGet to the fiddler proxy server to see precicely the requests that proget is making as well.

Hi, Great thanks. Just what I needed. I couldn't work out how to get the list to work. David

The Jenkins / ProGet Plugin has been updated to Version 0.3 with the following changes: Expand variable correctly Some basic validation on the version number If you update, then it should work!

If the feed is reporting "healthy" that means that an initial check passed. The 500-status errors will be logged on Admin > Error Logs; without seeing those, it's not really possible for us to advise on what the issue is. Hopefully that will give insight as to what could be failing. You may need to attach a proxy server between ProGet and MyGet (e.g., install Fiddler on the server, then point ProGet to use the Fiddler proxy), in order to capture the traffic.

I updated the default schema on the security group I was using to dbo and I was able to run a successful install. Thank you!

I know this is a really really old thread but I thought I would share something that we did for our continuous integration builds / deployment process. Every build drop location for each build definition will contain a "Latest" folder in addition to the "versioned" folders that contains the output of each build. At the end of our build template, we perform the standard activity of placing the build artifacts in the versioned dropped location. For SUCCESSFUL builds, we copy the contents of the drop location and update the "Latest" folder. If a build fails for some reason, we leave the contents of the Latest folder alone. Our nightly automated package and deployment processes (for automated integration testing) have been simplified to always pull from the "Latest" folder. They can determine if the folder contains the same version as the last one or if it's been updated.

After upgrading both the ProGet VM and our (potentially underpowered) Active Directory VM to more cores/more RAM, we seem to have worked around the issue. Thanks for the tips!

Looks like there was a packaging issue with the 1.2.0 installer. We'll get a fixed installer posted right away, but you can fix in the meantime by going to the Otter install directory (default is Program Files\Otter) and copying the lib and NativeBinaries directories from the Service directory to the Web\bin directory.

Can you share both the .nuspec and packages.config file? That would help quite a bit.

ProGet is designed for enterprise/organizational package management, and this is simply not a requirement or desired at all in those environments. So, it's highly unlikely we will add first-class support for this. Some organizations have created custom user directories for this purpose, which is possible with the SDK. Note: if you are a component company, you may want to contact us to see about partnering. We work with a handful of component vendors who use ProGet as a "back/middle-end" and then have a very simple customer-facing front-end on top of ProGet that integrates with their CRM, authentication, etc.

This is not currently supported. If you are a component company, you may want to contact us to see about partnering. We work with a handful of component vendors who use ProGet as a "back/middle-end" and then have a very simple customer-facing front-end on top of ProGet that integrates with their CRM, authentication, etc.

Has .lib files been tested as yet? We are experiencing the same problem with the source server. Can we please get confirmation if this is supported?

Hi, Version number for the Windows agent shows 34.0.0.1 in add/remove programs. '#justsaying' David

Well, we are closer at least. Yes, that does appear to be a regression - fortunately all it really does is wrap the "zip" CLI tool, so as you've discovered you can work around with Exec pretty easily. Regardless, we'll be sure to have the zip operations fixed for Linux in the next update.

BuildMaster is licensed by users, so you can have as many servers as you'd like.

This was a regression in 4.1.2, but it is fixed now in 4.1.3.

Aha! That's the ticket -- setting ErrorOutputLogLevel to "Warning" is just what I was looking for. For some reason I had thought the option would do the inverse (e.g. elevate warnings to errors). Thanks a ton for the help, -J

Hi, DOH! Yes, thanks, that's it. I'm blaming the person that wrote the original script I copied :-) Thanks again for your help. David