Do you have access to the SQL Server that BuildMaster is using? Can you send the results of the following query to support-at-inedo-dot-com: SELECT * FROM Providers Most importantly, the Provider_Configuration column.

The Database Connections module is designed to segregate connection strings in this exact manner; this way, only certain privileged users can use the database connection their privileges allow. In this case, it might make sense to build a custom Database Provider that's based off of the SQL Server one. This is pretty easy, and several users have done this. Please contact support, and we will send the source code for this.

We just released our TFS2012 extension - http://inedo.com/buildmaster/extensions/tfs2012

This is not possible with that setup. If the DLLs are deployed separately at times, they should really be their own deployables (or even applications in some cases), that way you can specify them to be deployed at the release level. However, for your case, you may be able to get away with creating multiple variables (e.g. FILEMASK1, FILEMASK2, FILEMASKN, etc.) I'm not actually sure if that will work or not, and still wouldn't solve the problem if you have more than N files.

Yes we do support other regions, we will file this as a bug targeted for the next release. Thank you for the report.

I will also add that there is a feature in the pipeline named "Release Archiving", which will allow deployed releases to be archived and delete the artifacts from a release for all but deployed builds. It will also delete the execution logs and messages for non-deployed builds. This feature (at the moment) is not scheduled for any particular release, but it should be coming in one of the next few minor (3.X) releases.

Great - working well! Thanks

At the moment, there is no way to accomplish the pull method. Our agents are extensible, but the BuildMaster service itself is not equipped to handle the incoming connections since it works backwards to the original design. We have however thought about implementing this type of agent specifically to allow for hosted instances of BuildMaster. If you are a looking to purchase the enterprise edition, there are additional support plans that we have done in the past that would expedite the delivery of features like this. If this interests you, please contact support@inedo.com.

Yes, deleting and readding the action step fixed this bug. I should have tried that, I suppose. Thanks! Matthew

We currently have no first-class integration with HPQC but we're always looking for ways to integrate with third-party tools. We even offer extended support plans that can move the integration to the top of the list so to speak. If you'd be willing to email us at support@inedo.com with ideas on the sort of integration you're looking for, we'd be glad to take a look at that.

Okay, thanks for letting me know. I did change the name through the database, and that worked just fine. The history of the rename is not as critical to me as the deployment history, so I think we're good for now. Thanks for the reply, Matthew

The 1000 is a limit imposed by Active Directory presumably for performance reasons. Typically, you shouldn't ever need to be on the users page when using Integrated Security because once a user is assigned privileges via the "Assign Security Privileges" page, they automatically become a named user if there are licenses available when they visit the BuildMaster URL. We are planning an enhancement that will determine based on the assigned privileges whether the user should be approval-only or full, but for now it will default to full (if available) and downgrade to approval-only if no full user licenses are available. Once the user has become a named user, you can manually edit the type of user on the "License Key and Activation" page which allows you to select "[change]" to toggle the user between full or approval-only as needed.

That solved it, thanks!

Are you using the integrated web server? If so, you'll need to add the host name: http://inedo.com/support/kb/1014/changing-buildmasters-url-with-the-integrated-web-server It's also pretty easy to upgrade to IIS, if it's already installed on the box: http://inedo.com/support/kb/1013/hosting-buildmaster-through-iis-instead-of-the-integrated-web-server

Yes I could definitely help test an extension.

Thanks for the update; we do plan on supporting this soon once a particular feature ("Release Archiving") is introduced. In the mean time, we can at least change some of the procs/funcs/etc that are crashing. If you can send us a backup of your database (support at inedo dot com), we could use that as a starting point and get a patch to you very soon. If you need to scrub sensitive data, this will do it: DELETE BuildExecution_PlanActionLogEntries UPDATE Providers SET Provider_Configuration = NULL UPDATE PlanActions SET Action_Configuration = NULL But it will also ruin your database, so obviously only do that on the database you'd send us :-)

I think the problem may have to do with your project/solution configuration (i.e. .sln and .vbproj/.csproj files). In the action's execution log, you can see the exact command run by the Action. I would suggest to run that command at your desktop, and then try to see what specific project is missing the output path... and then tweak the project files.

Yes,I would think the same. Thanks for clarifying. Please plan to release this fix at the earliest possible and would be glad if you can keep us informed on the same. For now, building .NET projects is really turning out to be a painful task just because of this one issue. Fortunately, there are some tedious workarounds.

The second issues I posted, has got fixed when I changed the regional settings to UK and now I am able to set a date in the datepicker control! Please fix this issue in next release guys. The first issue might well be because of the web site settings. Weird thing is the BuildMaster website was in 2.0 but the root websites setting was in 4.0. I ran aspnet_regiis -sn WSVC/ on all the paths and changed everything to 2.0. Did a IISreset but still didnt work ! But after doing that,I uninstalled and reinstalled the BM and it is working now ! Thanks for the help but please investigate the issue and would help if you can publish the corrrect IIS settings in deployment guide.

Configuration files must be associated with a deployable, which means you need at least 1 deployable in your application. Some of the differences between a deployable and an application are highlighted in this article: http://inedo.com/support/kb/1032/the-difference-between-deployables-and-applications For now, just create a deployable with the same name as your application and then you'll be able to create a config file.