I am using Vault/CruiseControl combination for build. After Vault was upgraded to 4.1 Version, the build broke, because some of the 3-rd party libs could not be retrieved from rep. I use the following lines for that task in Nant script:
<target name="fetch_3rdparty">
<foreach item="String" in="boost, UltimateToolbox, zlib" delim="," property="sub_dir">
<!--Set the login options: username, password, and server url URL="http://vaultserver/VaultService-->
<vaultsetloginoptions user="${vault.username}" password="${vault.password}" URL="${vault.url}" />
<!--Connect to NantTestRep-->
<vaultsetrepository repositoryName="${vault.repository}" />
<!--Set a working folder.-->
<vaultsetworkingfolder repositoryFolderPath="$/deverse/${sub_dir}/" diskPath="${vault.working_dir}/${sub_dir}/" createDiskPath="true" />
<!--Do a get on the working folder.-->
<vaultget>
<vaultfileset>
<include name="${vault.working_dir}/${sub_dir}/" />
</vaultfileset>
<getoptions Recursive="true" />
</vaultget>
</foreach>
</target>
Could somebody explain to me why on Earth this works for Zlib and UltimateToolbox, but does not work for boost? What could possibly be a catch here? the only difference between boost lib and other 2 is that boost has another 'boost' folder in it. in other words, it is 'boost/boost/blah-blah... But how could this be a problem?
Problems with checkout for build
Moderator: SourceGear
Re: Problems with checkout for build
You also sent us an e-mail, which I forwarded to one of our developers, it's case 216930. We'll be in touch soon.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager