Thanks for the bug report. We've just published v4.3 of the NUnit extension which should resolve this issue.

You might be able to get away with this with some git trickery, i.e. you can have a script at the beginning of the deployment plan that lists the remote branches and gets the latest commit time for each one, and writes the branch name out to a file (or something like that). Then you can use the "Set Variable Value from File" action to save that value into a BuildMaster variable, and reference that in the "Get Latest" action. Hope this helps :)

Tod. Looks like whatever you discovered was right. Added an exclusion of example.org, and I can now query and cache through a ProGet feed

As of BuildMaster 4.9, many of the restrictions in the express edition have been removed. #####Features Available Only in Enterprise Edition (4.9 and later): Enterprise Support Active Directory / LDAP Integration #####Limitations of Free Edition (4.9 and later): 5 Users 10 Applications 5 Servers The following information is outdated, but remains for users of older versions. #####Features Available Only in Enterprise Edition (4.8 and earlier): Enterprise Support Active Directory / LDAP Integration Automated Promotion Requirements Change Controls Configuration File Templates Database Change Script Deployer Deployable Dependencies Group-based Approvals Multiple Active Builds Scoped Privileges Server Groups/Pools #####Limitations of Free Edition (4.8 and earlier): 5 Users 10 Applications 1 Automatic Build / application 1 Configuration Files / deployable 1 Database Connection / environment & application 3 Deployables / application 1 Workflow / application 3 Environments 1 Imported Deployable / application 2 Issue Trackers 5 Servers 3 Source Control Providers

I tried that. Actually, the stop/start link started showing after I restarted the app pool and website. Please, keep me in touch for a solution. Thanks

It goes back to Day 1 of your install; you can query the table directly (it's [EventOccurences]) if you need to do some complex searching.

There is a bug in 3.7.x that will be fixed in 3.7.4 On the proxy configuration page, can you enter a dummy value into "Exclude URLs" section, e.g. "example.org"?

No problem! Now for a barrage of questions... Where is the 503 response coming from, ProGet or the proxy server? Is there an error message in addition to the status code? What do you mean by "use the ProGet feed", does that mean browsing the ProGet web application (i.e. feed overview page), or accessing packages via nuget.exe/Visual Studio? And does it work as expected if you access ProGet over HTTPS?

This can be done as a Promotion Requirement by implementing the PromotionRequirementBase; this class basically just returns a PromotionRequirementStatus that includes a text description and a PromotionRequirementState indicating if the build is eligible for promotion. If you'd like to see how any of the built-in promotion requirements are implemented, feel free to use Reflector or another disassembly tool, or just ask us for the source code for those items.

You can with URL-triggered builds, simply supply the query string argument buildNumber when triggering the URL, and that number will be used instead. For hourly/daily builds or SCM-triggered builds, the only way we could accomplish something similar to this is by modifying the extension to set a build variable.

Do you mean that some symbols are being indexed while others are not?

My bad, MyInedo acc gives that.

I see. Thanks for the feedback - I didn't think about retention but that is a very good point. Retention itself is also a relatively new feature for ProGet, and we are still evaluating whether it ought to be included in the free edition in some form. Regarding feed-specific override paths, we probably will add this in a future release, but I can't give you a specific version as yet.

Hi Wajeeh, It looks like there is definitely something wrong with your database; probably, the stored procedures are being created under different schema (i.e. not dbo). If this is the case, You can rectify this by dropping the database, and then running the bmdbupdate.exe tool from the manual install packages... but it's probably easier to uninstall, drop the BuildMaster database, and then reinstall.

I've read that NuGet's architecture is being redesigned for version 3.0, which should also improve the performance. http://blog.nuget.org/20150608/nuget-server-status.html http://blog.nuget.org/20150601/nuget-3.0-rc2.html

Please see the TFS extension for information on how to do this.

Thanks for your prompt reply. The patch script you linked certainly fixed Issue#4 for us. I think we should be fine to push forward with 4.7.3 as it looks like all the issues have now been resolved. Thanks for linking through that knowledge base article. I'll be sure to have a look through the knowledge base articles before any future upgrades.

Hi Simon, The variable matching isn't taking place because you're using the simple syntax (see "notation" under Variables Documentation). Specifically, BuildMaster is looking for a varaible named "DeployableName_", which doesn't exist, and thus it is replaced as a literal. So, either change to "$DeployableName-$BuildNumber" or "${DeployableName}_${BuildNumber}". Alana

The INEDOPROGETSVC service is used by ProGet to perform background tasks (indexing, cleanup, etc) and is required to run ProGet. The only options (right now anyway) to install the ProGet web application are: IIS-hosted Integrated web server (this is essentially a 2nd Windows service) Linux via Docker (currently v4.0 in beta)

This problem is a pretty big deal - it means that existing TeamCity build artifacts can't be "pulled" into ProGet. The only way to make it work is for new build output, pushing nuget output to ProGet. That's suboptimal.