We tried to reproduce this, but I get this output, which doesn't include "arguments" and which doesn't put a trailing slash after the destination directory: INFO : 2017-02-22 17:50:04Z - Executing SVN export... DEBUG: 2017-02-22 17:50:04Z - Using TcpAgent agent on GODZILLA DEBUG: 2017-02-22 17:50:04Z - Working directory: DEBUG: 2017-02-22 17:50:04Z - Executing: C:\ProgramData\InedoAgent\BuildMaster\ExtensionsTemp\Subversion\Resources\svn.exe export "https://github.com/Inedo/bmx-subversion/trunk/" "C:\ProgramData\InedoAgent\BuildMaster\Temp\_E78\_D0" --non-interactive --trust-server-cert DEBUG: 2017-02-22 17:50:12Z - A C:\ProgramData\InedoAgent\BuildMaster\Temp\_E78\_D0 [snip] DEBUG: 2017-02-22 17:50:12Z - A C:\ProgramData\InedoAgent\BuildMaster\Temp\_E78\_D0\packages.config DEBUG: 2017-02-22 17:50:12Z - Exported revision 63. INFO : 2017-02-22 17:50:12Z - SVN export executed. Caan you submit the plan and logs in a ticket? Tjhis will be much easier for us to research.

Thanks for the clarification; I was able to repro this and logged a bug report (BM-2371). It will be addressed in a future maintence release.

This is exactly what I was looking for, thank you!

We will implement this eventually once we have the specs nailed down. The plan is to offer a per-variable setting (in the same vein as the "sensitive" option) so it shouldn't break backwards compatibility.

Yes that is a bug then. I'll submit a bug report.

i'm afraid we won't be able to help with that; please consult with the BizTalk ESB team or forums.

That makes much more sense! Thank you for the clarification. So I effectively do not need to specify targets in any of the Buildmaster actions that would require that information. Thanks for your help Tod

I'll put a note in to add this to the next maintenance release this week.

There is no way to configure that in the schedule, but you can somewhat accomplish this by either: setting the filter to "newest active release" and moving the release to the top on the Release Sequence page or, if you don't mind multiple failed builds in your release, setting the filter to "all releases" and filtering at the top of the build plan, e.g. if $CompareReleaseSequence(!=, $ReleaseNumber, $DesiredReleaseNumber) { Log-Information `$ReleaseNumber is $ReleaseNumber, skipping.; fail; }

I found the solution. I had tried several different ways but finally found the right way. Just putting folder/job/jobname in the List Source made it work. The list won't auto show the job but you can type it in and it works.

Release template values are currently only used by the user interface, as a means of assisting users enter key/value pairs (variables) for a release or package. They API does not reference these, but you can pass variables into the APi quite easily.

Yes of course, smacking forehead now! Thanks!

I see. Is it possible to leave a reminder of that limit on UI somehow? Like how many characters left that kind?

This was indeed removed from v5 for a variety of reasons, but we do plan to bring it back. It was very problematic to display this information on the web after connecting to it from an agent, etc.

Ah, good find. The file browser is the only component of the web app that would use the SSH client directly, and it looks like those dlls just aren't getting packaged correctly in the installer. We'll put this on the list to fix.

Alana, Might I suggest updating the documentation to state that. Currently it is specified for the Upload operation but not the other two.

ah yes, sorry. I setup the creds a couple of months ago and forgot about that option. thanks.

Unfortunately i'm not familiar enough with CakePHP to advise on how to stop the service non-interactively. I would perhaps suggest to modify the batch file to not look for an exit code? BuildMaster will basically just run whatever process you ask to, so the batch file is what's waiting...

Hi Tod, Thank you! I'm never sure if I'm being helpful or just getting in the way. Just can't sit still long enough :).