Invalid XML returned to CruiseControl.Net

[mriffey]

It appears that the CruiseControl.Net Vault interface is creating bad XML, which then results in important output being buried in the build log vs showing up on the dashboard.

Ive attached a screenshot of the invalid XML from a fairly uncommon issue.

Ive included a few simpler (and far more common) examples below.

Any suggestions on how I can resolve this? ("fix the vault plugin code yourself" is a valid response)

Thanks!

Mark

Code: Select all

<buildresults>
  <message><vault></message>
  <message>  <result></message>
  <message>    <success>True</success></message>
  <message>  </result></message>
  <message></vault></message>
</buildresults>


<buildresults>
  <message><vault></message>
  <message>  <changeset></message>
  <message>    <ModifyFile></message>
  <message>      <id>0</id></message>
  <message>      <repospath>$/BCUVersionControl/DatMailTest/BCUBuildStatus.xml</repospath></message>
  <message>      <localpath>C:\Clarion73\projects\BCUVersionControl\DatMailTest\BCUBuildStatus.xml</localpath></message>
  <message>    </ModifyFile></message>
  <message>  </changeset></message>
  <message>  <!--Preparing data to begin transaction--></message>
  <message>  <!--Beginning transaction--></message>
  <message>  <!--    Check in $/BCUVersionControl/DatMailTest/BCUBuildStatus.xml--></message>
  <message>  <!--Ending the transaction--></message>
  <message>  <!--Transaction completed successfully--></message>
  <message>  <result></message>
  <message>    <success>True</success></message>
  <message>  </result></message>
  <message></vault></message>
</buildresults>

[Beth]

It doesn't look like Vault is adding the message tags. We're looking into this a little more and might have some suggestions.

[mriffey]

It doesn't look like Vault is adding the message tags. We're looking into this a little more and might have some suggestions.

Thanks Beth. Anticipation mode=On:)

[mriffey]

Beth,

A little more information might be helpful...

These vault steps are being run via the exec CC.Net command. For example:

<exec>
<executable>C:\Program Files (x86)\SourceGear\Vault Client\vault.exe</executable>
<baseDirectory>C:\Clarion73\projects\DatMailTest\</baseDirectory>
<buildArgs>Get -host wbk-safe01.windowbook.local -user xxxxxx -password xxxxx -repository wbClarion -merge overwrite -makewritable -backup no -performdeletions donotremoveworkingcopy $/BCUVersionControl/DatMailTest/</buildArgs>
<buildTimeoutSeconds>$(VaultTimeout)</buildTimeoutSeconds>
<successExitCodes>0,-1</successExitCodes>
</exec>

We use the cc.net integration, but in this case, it needs to be done in this manner - and this type of use is fairly widespread.

Mark

[mriffey]

Is there any update on this issue?

[Beth]

What's happening is that CC.NET is putting in the message tags. We have someone checking into a work-around, but it will take some more time.