The Click Once Action is essentially a wrapper around mage.exe; you can see exactly how this is wrapping that utility in the source code: the source code, and what those options mean at msdn. The AppCodeBase is the deployment root of your application in IIS, generally "/", but it could be "/MyApp" or something as well. If you specify "CopyFiles" in the action, then the application files and manifest will be in whatever target directory you specify. If you do not specify a source and target directory, then the default/working directory will be used for both (which means the output will be exactly where the input was -- in the $CurrentDirectory).

Ah, I see -- everything is logged to that in the database, there are no additional files. The error log is primarily for diagnostic purposes, and sometimes errors are expected. That particular error, for example, it sounds like your server is trying to connect to Inedo.com to see the available extensions. It's OK if you can't do that, but, that's where it's logged.

Alex, different Workflows, of course! Sorry I should have thought of that. Thanks!

Hi, I'll try to answer the various questions here... When that publish completes successfully in TC, can we easily 'start' a build to DEV integration environment. Yes, for this , you may want to use a "URL-based Trigger" to import the build files from TC. Lastly, can we schedule a PROD release once we are done for hte middle of the night and have it alert us via text if it fails? You can schedule the promotion / deployment, and set up an event listener to email you on failure. These are extensbile, so if the SMS is needed (instead of email), you can either have a script call an SMS gateway or write an extension to do that. In addition, we don't like the non-graphical configuration, etc of bathc files as it is not overly intuitive (but works fine). Please let me know how this would work in your environment. Sure, you can run a batch/cmd file... unless it's prompting for input (like by using PAUSE command) or doing other things that can only work interactively. But, you'll find out quickly what works / doesn't. Sometimes it will be easier just to use the built-in actions in BuildMaster. Originally our organization mandated octopus, but has since undone that mandate, so I'm trying to see what options I have...The challenge is in general we have it working, so cost may be the reason we don't convert, but that is something to understand after a POC. For a comparison check out A Comparison: BuildMaster vs. Octopus Deploy .

This is likely an incorrect error that's being reported; next time you see this, just try to restart the web app by going to, Admin > All Settings > Save. This will re-establish a connection to the service on restart, and should clear this error.

This is fairly easy to reproduce -- just turn off the SQL Server. As to why it's happening, that's hard to say... perhaps it's being rebooted? Or you have network connectivity issues? If this is happening, I wouldn't disable pooling --- instead, just try to restart the web app by going to, Admin > All Settings > Save. This will re-establish a connection to the service on restart, and should clear this error. Another thing you may want to do, is to configure the service to crash on database errors; then set auto-recovery. You can do this by setting a value in your service's application configuration file, "CrashOnDbFailure" to "True", and changing the recovery settings in Windows.

hi, I'm not sure I understand the question? But, you can set up multiple database conenctions in your application, and pick the ones you want to use... either directly or with a variable.

Hi, yes -- There are quite a few users that have BuildMaster to do just that. I'm not sure about the Oracle/SOA services, but if it's something that you can write in a quick script, then it'd be fairly easy to add as an action as part of your deployment plan.

In order to do this, you'll need to set up a separate configuration profile. you can do this in Admin > Extensions > TFS.

Here are the actions that aren't supported via SSH agent currently: Unit Test Actions HTTP Reporting Actions Generate Release Notes Action (unless running on BuildMaster server) Execute Database Change Scripts Action Rename Files Action (shell script is recommended for this) Set File Attributes Action (shell script is recommended for this)

You can just edit the workflow step and select the deployment plan you want for that particular workflow step. There was a bug fixed in the v4.7.4 version that caused this behavior, typically when combined with Build Steps and multiple workflows. If you upgrade to the latest maintenance release for your minor version (i.e. v4.7.5) the copy should work as designed in all cases.

Yes, that's correct; if your doing this with a custom extension, then you can use the "StoredProcs.Variables_CreateOrUpdateVariableDefinition" method directly, and pass null in where appropriate.

In the v5 plans (which we will ship in 4.9), you can have "output variables" from your powershell scripts. But currently, you can't communicate back to the BuildMAster execution engine via a script with anything but exit codes.

The page was changed in v4.8.2 to only show the first 30 releases for perf reasons, so if you have more active releases than that, the list would be truncated to the first 30 ordered by when they were created. We're open to making this behavior configurable instead of a strict limit of 30.

The Build MSBuild Project actions effectively just run msbuild.exe against your project files; so, I would start there. KB1052 offers some troubleshooting tips, see the "Issues with third-party tools and integrations" section for how to dig into the details.

i have 2015 team explored installed but not succeeded in same schenario.

I'm afraid I don't have enough information to help diagnose this problem. Please keep in mind, BuildMaster isn't actually looking for anything -- it's essentially just executing a third-party tool like nuget.exe and msbuild.exe with the arguments you specify, so it's important to look at both the arguments to those commands and the working directories those commands are being run in. These will be logged near the top log for the action.

Is there any other error information e.g. stack trace or error details? You can look in the Windows Event Log for more info.

the error was not occuring when trying to select project. Browsing worked perfectly, i was able to browse and choose my SLN file. the error occurred upon clicking "next". All that aside, installing .NET 4.5 seems to have resolved the issue. 4.5 is not a requirement for vault or for BuildMaster, but seems to have changed something. I found an unrelated artical on google saying that they were getting a MaxArrayLength error, and that the error went away after installing .NET 4.5, so i figured it was worth a shot, and sure enough issue resolved!

Sure, happy to share the source, though you're welcome to use a disassembler or reflection tool as well -- easiest thing would to fill out the Source Code Request and we'll email it on over. If you only ever had a single, well-known database to work with, then hard-coding the connection string isn't too bad of an idea. You can always just update the code and redeploy the extension if it ever changes. But since you have multiple databases... I'm not sure if it's the best approach. Otherwise, consider that any property on your class that you mark with the Persistent will be displayed as a textbox and it will be available at runtime. So, two ideas come to mind: You could have a ConnectionSTring property, and just use that; that would be quite easy You could have DatabaseConnectionName property, and have that reference a database connection within your application; these are used to deploy database changes The DatabaseConnectionName will be a little trickier, as you'll have to retrieve it from the database, then deserialize it, then look at the object's connection string property. All of the Database ACtions do this, so you can look at their source code. You'd only want to do this if you're already using database connections.