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 :-)

Yes I could definitely help test an extension.

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.

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.

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.

When you share/link action groups, you may select a "Default Server" for the actions, which means you can link them across environments and still have the actions run on different servers (just select the local BuildMaster server for the actions, that will be overridden by the selected default server of the group). If you choose a separate build server for your actions instead, that will take precendence over the default server unless the build server is the same as the BuildMaster server; if that's the case you can just put those actions in a separate group. As for the database selection, we could update that action to allow selection via a variable or have a default option that chooses the DB based on the environment it's in.

Thanks Steve. That was enough for us to implement a custom action, and the action were pretty easy to implement based on the source code that you provided. Appreciate the prompt response!

Thanks for the confirmation. I just tested this technique, and it worked really well, actually. I'm going to use the following naming convention: DEV SQL Server (the actual DEV database) TEST to DEV SQL Server (the TEST database available to the DEV BuildMaster environment) PROD to DEV SQL Server (the PROD database available to the DEV BuildMaster environment) I was concerned that BuildMaster would want to re-initialize the database, but it didn't. In fact, during the next build in DEV, BuildMaster correctly backed up my PROD db and restored to DEV and then determined that my SQL Change Script had never been run (since the BuildMaster execution table is also restored). This is how I expect and want it to behave. Thanks again for the VERY FAST response! Matthew

Yes, I would like a comments field for when I deploy a config file. I already liberally use the comments field when editing. Thanks!

FYI we have released a new version of the DotNetRecipes extension, if you update that extension within BuildMaster then re-create the example app, the signing should work correctly. As for the certificate hash problem, that has been resolved in the .NET extension which is scheduled for a release later today or early tomorrow.

Thanks look forward to it

Ah. Currently on 2.6. Will upgrade immediately!

My fault, I had forgotten about the shared TMP directory and was focused on the WRK and SRC ones. It appears then that building the same app but different workflows at the same time is not currently supported, but there are workarounds. As an example, you could use a different environment (e.g. Integration2) for the patch workflow, then link/share all the action groups from Integration. If you were to then install a BuildMaster agent on the BuildMaster server (and add it via the Servers page), that agent would have its own set of temporary directories. All you'd have to do is update the "default server" setting for each action group in Integration2 to point to the agent server.

Yes, but not easily. Automatic build records (schedule, SCM-triggered, or URL-triggered) are not "soft deleted", so you must go to the audit logs and search for the "BSHDEL" event. This can be done from the UI or directly from the database with SELECT * FROM EventOccurences WHERE Event_Code='BSHDEL'

For future reference, this was happening because the application attempting to be built was including an imported deployable, and there was no active build in the referenced application. The error message will be clarified in the next version of BuildMaster (v3.2.2).

Thank you. The server was activated fine and is working very well. I am satisfied.

Do you know if you are running the BuildMaster web application through the integrated web server, or if it's hosted by IIS? For the integrated web server, ensure that its service runs under Administrator as well. If you're using IIS, you'll have to verify that the app pool's identity is running as the Administrator account in addition to the BuildMaster service. Right now we are in the process of writing a knowledge base article that will give step-by-step instructions with regards to connecting to GitHub since that seems to be the most common hosted solution for our Git integration.

If you're using the integrated web server, can you verify that the "BuildMaster Web Server" service is started? (Start > Run > "services.msc" to check, if it's not, just click Start). If you're using IIS to host the BuildMaster site, can you verify that the site is started and the BuildMaster app pool is running?

The Branch Action is designed for "tagging" builds (Subversion and CVS), and actually, it's been renamed in 3.2 and will only be displayed if you have one of those providers. You're definitely on the right track for labeling each build, but merging... it's not really something you can do on an automated basis because of conflicts. That said, if you do want to merge, you can simply call tf.exe merge.