If that were to happen, then you'd need to follow the instructions here to restore it. Resetting the Default Admin Account If, due to a configuration issue, you find yourself locked out of ProGet, you can reset the built in Admin account to its default password and reset ProGet to use the built in directory by running ProGet.Service.exe and selecting the ResetAdminPassword option.

FYI - there is now a 30-release limit as of v4.8.2.

With remote connector caching enabled (default is enabled), there is almost no reason to pull a package to your feed. The reason the Pull feature is there, for example, is so you can pull down your "approved" packages, then remove the connector which in turn makes that package part of your local feed. Anyway, pulled packages are keyed by ID and version, so if a new version were released, you'd have to pull that. Check out some of the features we have planned on the Road Map which will better handle scenarios for users who pull packages often.

I don't believe the "Application Modified" event is particularly useful because that simply means a field on the Application Settings page was changed (like "allow multiple active releases" was checked), and I can't think of a good reason you'd want to know when an individual setting like that changed beyond who and when since you'll notice the changes as you use the application and can refer back to the event log then. That being said, I do agree that things like deployment plans being edited should show exactly what changed... and that feature is scheduled for BuildMaster v5; check out the Road Map for more information.

You can perform any action on the BuildMaster (local) server, or on a remote (agent) server. It's quite common to use a dedicated build server (via an agent) to compile source, etc).

Please see the Features by Edition page.

Thanks for the report; in this case, the correct behavior is to not display the log-in form at all when Integrated Authentication is enabled, and instead give an error page indicating no access. I've logged this PG-435

All fixed and I finally realized what I was doing wrong the admin password, need to learn where my uppercase characters go in passwords! Thanks, Jon

Hello. What we noticed is that when we receive this error if we delete the nuget package in the feed and then reload it the problem disappear. We still have a legacy feed. Do you think that info could be relevant?

Most definitely; it's a must-have as we transition from a "private NuGet server" to a "private repository manager". I suppose we should explicitly list it under "New repository formats". I'll add a +1 to our (internal) tracker!

Ah; well, that would explain it :) Your PDB files contain no links to source files, which VS and ProGet are unable o index/locate them. This means you'll need to adjust your complication process to incluse them. A quick search surfaced this article, which may be of assistance: Correctly Creating Native C++ Release Build PDBs. Please do post an update if you find the issue/setting in your project/build file that prevented this from happening.

This will be the simplest resolution. First, upgrade the database instance to SQL Express 2008 or 2014; this will increase your limit to 10GB. Just download and run the installer from Microsoft, and instruct it to upgrade the instance. Then, upgrade to BuildMaster 4.8, which will have retention policies that allow you to delete/purge execution logs (which are taking a lot of space).

Thanks, all good now.

Actually, one more comment re: this. It appears that the package ID is synonymous with its name. I thought there was a separate ID value. When I grabbed all packages and versions and tried to serialize in PowerShell, it failed due to the size of the content, so it was good to discover that I can query for the specific package name/ID.

This sounds like it's an issue with your workstation communicating with the server; the 400 indicates a problem with WIndows/NTLM authentication. That's not done by ProGet, but it's handled by IIS/Windows. It could be a whole lot of things, from system clock being off by a few minutes to domain/security issues. Unfortunately there's not a whole lot we can help with, though i'd suggest to search "Windows Auth not working" while including specific messages you're seeing, and try to narrow down form there. Please share what you find, as someone else might come across the same configuration problem.

If you don't specify the symbols option, but include everything in a src directory, then it will work. Keep in mind a NuGet package is just a zip file, so if you're having trouble using nuget.exe with nuspec files and native packages, then you might find it easier to workaround by creating the zip file. Just remember to follow the conventions.

Yes; this would ultimately be done through the typescript compiler (tsc.exe), so it really depends on how you plan to build/use them. For .NET projects, it's something that msbuild calls, and you can specify whether or not to generate the .d files in the project properties. Otherwise, you could simply call the tsc.exe directly with the desired parameters. ONce you have those, you can capture the artifact from there.

It can do that, but it won't automatically. You have to configure the deployment plans. Think of the deployment plans as a script that will run each time you deploy to an environment. For stored procedures, those should be treated as code and kept in source control, as they can be recreated simply with a DROP/CREATE/CONFIGURE script file. This way, they can be redeployed like any other artifact (i.e. extracted to some directory and executed from disk). As mentioned in the previous post, DDL/DML database changes cannot be automatically rolled back because once you DROP a column, it's gone for good until you restore from backup. Configuring a deployment plan to take a database backup is probably a good idea in this case :) You could go one step further and configure the deployment plan to restore from that backup on some condition if you really wanted to, but I would hope once the deployment is automated that these failed deployments will be kept to a minimum.

Yes; BuildMaster can do anything it is configured to do in its Deployment Plans. There's a few backup strategies you could use: zip contents of target project and move it to a backup folder deploy to a target directory then swap directory names deploy straight from a BuildMaster artifact, then a zip backup would be kept automatically (recommended) The 3rd option gives you a pretty easy way to rollback, provided there aren't API-breaking database schema changes (you'll have to restore the DB in that case, since you can't unDROP a column). See the following for more information on rollbacks: http://inedo.com/support/tutorials/performing-a-deployment-rollback-with-buildmaster