UPDATE: This limitation no longer exists in BuildMaster v5 (OtterScript) Plans. There is no limit to the number of executions that BuildMaster can run in parallel; however, only a single remote action can run on the same remote server/agent at a time. This means that, for example, if you create a build of multiple applications at once, and all of them build on the same build server, only one of those applications will be built at a time. You can improve this behavior by using server pools if you'd like if you have multiple build servers you would like to utilize. In exceptional cases, you could install multiple agents on the same machine (on different ports), and put those in a server pool.

I had the same issue, Resolved by uninstalling sql server 2005 ,restarting the machine and reinstalling buildmaster as admin

It's not a deployment action anymore (it used to be though). Now it's a "Post-Build Step" (which is essentially an Event Listener), and can be set on the Workflow Overview page.

As written now, that promotion requirement is a very simple text-based match - anything more complicated would require a custom predicate.

I think I see why this is happening... it appears the extension is escaping all data in the URI (which would include the equals sign and ampersand): https://github.com/Inedo/bmx-jenkins/blob/956f738173f0cde0ffff4cdef1e6a19ae5e5de66/JenkinsClient.cs#L107 We should be able to fix this and release a new version.

The latest release of the Jenkins plugin that fixed a bug with the url parameter encoding also fixed the authentication issues.

We've published the BuildMasterBeta extension v4.5 which contains a fix for this. You can install this extension from the Admin->Manage Extensions page. This fix will also be included in the next maintenance release of BuildMaster, which will be 4.6.3. Thanks for the bug report!

I've figured out what I would like to see and its an approach I've seen other tools take. I think you need a BuildMaster plugin for Jenkins that I can add as a build step in Jenkins to: Import ReleaseNumber as a variable Trigger a BuildMaster Job and a) send selected artifacts to BuildMaster, b) set the BM build number to the Jenkins build number (I just like to keep things in sync for traceability) Workflow SVN Commit -> Jenkins Build -> BuildMaster: Import Sent Files I'd then deploy to first environment (using the BM post build step action) which would do the deployment and then call test job in Jenkins to verify deployment and/or perform regression testing. I've got most of this working using groovy scripts, but it would certainly improve things if wrapped in a plugin.

This could be caused by a dropped named-pipes connection between the web application and the BuildMaster service. Can you try restarting the BuildMaster service to see if that re-initiates the connection? You can also try running the service interactively to diagnose (http://inedo.com/support/kb/1015/running-the-buildmaster-services-interactively). Also, it could be a server initialization error that happens before anything gets run - make sure you're looking at the Execution Details page for errors related to that instead of the "in-progress" page.

We don't have any plans for this at this time.

Thanks a lot! That was exactly the port that was set (and I was probably notified by the installer, but I couldn't find it afterwards)

Thanks for the pointers, Dean!

We don't have a formal EoL policy, but as long as you're current on support (which, just checked, you guys are), we'll do our best to provide support for whatever version you are on. Of course, please understand that, a lot of times, the answer may just be "upgrade to a new version", and we most likely will be unable to provide a hotfix. I suggest you upgrade to v4.6 (we can provide assistance in this as well), and then schedule a routine upgrade/maintenance window (monthly, bi-monthly, etc) so that you can try to keep current. We put a lot of effort into making sure everything is backwards-compatible, and in the event something breaks, you can rollback... or we have the capability to ship a new release within hours.

hallo farhan, wurden Sie TFS? können Sie versuchen, löschen Sie das Verzeichnis "GitRepositories" im build svctmp Ordner? Das sollte das Problem beheben.

This action has been updated in 4.6.4, which is now available. We've added a more friendly editor for form data and some better documentation in the action. The UI will probably still be refined in a future release, but it should be more intuitive now.

Hey Alana, That option sounds fine to me. I certainly think it would cut down the time to spawn up new Applications for us.

Sorry, this question somehow got marked as resolved, but it doesn't look like you ever got a response. If you'd like, you can email us at support at inedo.com with details about what you are trying to do, and we can try to give you some more specific help/ideas.

When you say "BuildMaster is not able to see it", are you saying you aren't able to get the latest files in that branch, or that when you browse the branches in the file/folder picker that they aren't visible? I just did a quick test with a Git repository on BitBucket and the moment I added a remote branch, it became visible in the file/folder picker.

We don't have any tutorials for this specifically, but you should be able to build everything using the "Execute Command Line" action: http://help.adobe.com/en_US/Flex/4.0/UsingFlashBuilder/WSbde04e3d3e6474c4-59108b2e1215eb9d5e4-8000.html

We have fixed this for v4.5.8. For users of v4.5.7, you may download a script patch here: http://44.inedo.com/buildmaster/v4.5.7-JS-Patch.zip This .zip file will contain a JavaScript file that should be saved in the \Resources\jQuery subdirectory of the BuildMaster web application installation. Its presence will override that of the existing DeploymentPlans.Common.js.gz file, and the page should refresh correctly once it's there (you may need to CTRL+F5 the browser once if it doesn't work right away).