We are using Solaris 10. It is possible the delays are being caused by poor performance of the Buildmaster server which is running as a virtual machine. I have raised a helpdek issue on our side to investigate as just copying the file with winscp from Solaris to Buildmaster takes 65 seconds which is too long.

Thanks, this issue is now fixed after updating the Jenkinds extension to the latest 3.1.2 version.

Thanks, we will wait for the updated svn extension, and use the execute command line option in the mean time.

Using !.svn* still creates the .svn folder on the destination machine.

The "Execute Command Line" option correctly handles the return code from the unix command so we can use this option, thanks. It would be good if the SSH Execute options worked, however, as they give us some more flexibility. Note, the target Unix platform where the return code is not handled is Solaris 10.

As it turns out this is a problem related specifically to the SVN extension and will require us to release a new version of the extension. We will have this out within the next few days. As a workaround, you can call the Execute Command Line action directly with the appropriate SVN checkout arguments in order to get the latest code.

This feature was actually added in v4.0, just change the workflow properties to allow deployments to any environment.

Thanks for the work around. Saved us much headache!

Just to update anyone reading this. Having spoken to support I was being a bit of an idiot. When prompted to select from SVN (Step = Select Provider/File) it wants a file, not a folder. So /Project/ will error, but if you pick a file in that folder all works.

Hi Tero, The MySQL Database Provider is just passing the script as a command to the database. I did a quick search, and it looks like it might be configuration (connection string) related. Does your connection string have "Allow User Variables=True" in it? http://dev.mysql.com/doc/refman/5.0/en/connector-net-connection-options.html Best, Steve

Are you planning on using IIS to host the BuildMaster web application? If so, you're all set. The IntegratedWebServer_ config values are only for hosting BuildMaster with the integrated web server. If you're going that route I can give you those values if you'd like. The "HasLoggedIn" value is only used to do initial setup of the example application and will be created and default to false if not present on the web app first load. The only table touched by the installer that would change its values is the configuration table - everything else database related is generated by the installer using the changescripter tool (bmdbupdate.exe) just as if you ran it manually against the DB.

That was removed on purpose. We are moving away from the Wijmo control toolkit we had used previously. For the moment, the time inputs will be simple textboxes until we find an easier solution.

There is no "application export" functionality since the goal is to have 1 instance of BuildMaster that controls the release and deployments from SCM through Production. The only things you can do at this point are re-create the steps manually, or play with the SDK to write a custom recipe that both exports an application into some format, and also can import it. Unfortunately we don't have any recipe creation tutorials at this point, but we could send you some code as an example you'd like (they're pretty simple if you already know C#). The best thing you can do would be to solve the infrastructure problems around the Production environment and allow BuildMaster access to an agent installed on the server(s) of that environment. This way you'd have a single instance of BuildMaster and would only have to manage a single deployment plan per application.

Hi Steve and Tod, Thanks for the information. At my next available opportunity, I will be testing my server to see if my ISP blocks SMTP transmissions. I read through the How-To you referenced on that topic, and it's a bit of a stretch for my experience, so it may take me a while. However, I will report back when I have results. Also, to Steve's question, we are using the latest version of BuildMaster, just updated prior to testing SMTP settings. To your point about two-factor authentication, I just checked my Google Account settings, and I am NOT currently using 2-factor authentication (though I probably should be). Thanks for the thought, though. I will do some more work and report back. Thanks again for the ideas. Matthew

Hi Jeff, Great questions. We try to deal with complex situations as simple as possible, but complex things can get complex. So, of course, "it depends". We're starting to document some of these in our specifics section ( http://inedo.com/specifics ) -- it's a work in progress, but we hope it gives some idea. The first step is to "translate" your organizational specific terminology to BuildMaster's terminology. We model software development as a whole, so we can implement really any structure process... it's just about figuring out what should be a deployable, what should be an application, etc. The "Release Management Done Right" whitepaper discusses the terminology we use. With only the information you provided, it's difficult to give specific advice, but from what it sounds like, the question is between Applications and Deployables. There's a KB article on the topic - http://inedo.com/support/kb/1032/the-difference-between-deployables-and-applications - that discusses differences. Dependencies are defined at the deployable level (AppX depends on EntFramework) and used at the release level (AppX 3.2 depends on EntFramework 2.0). This enables all sorts of complex patterns we've seen implemented. Feel free to contact us ( http://inedo.com/contact ), and we can discuss this in more detail and possibly help build a proof of concept. Best, Alex

Hi Tim, BuildMaster is licensed on a "per team" basis, so each user who accesses BuildMaster needs to have either a full or limited-access license. You can reassign users as needed, but not to workaround licensing policies. Hope that helps, Steve

The BuildMaster software itself requires a Windows Server and SQL Server database. BuildMaster can connect to and orchestrate Unix boxes via SSH-based agents.

Yes. Things appear to be working now.

The ScheduleExecuterThrottle value on the Advanced/Internal Settings page found under Admin determines how often this polling occurs (it also controls the polling for whether it's time to do a scheduled build). The field specifies polling frequency in minutes.

Thanks Alex. Changing the type/user credentials did the trick. John