I have the same problem occaisonally. But for me this happen on the first
nightly build where the label has a new number.
Is there any other cause of this problemem? Like bracnching Dev->Release
between builds?
/MrK
On Tuesday, May 18, 2010 7:12:27 PM UTC+2, Paul wrote:
> Hi there
>
> We have just upgraded to 1.5.7256.1 from 1.4.4 and we are getting the
> problem below. All our projects were building successfully but now
> as soon as they are rebuilt either by a force build or due to a
> modification the problem occurs. Setting applyLabel to false
> obviously gets round the problem but it means the builds are not
> labelled in TFS.
>
>
> System.Exception: Ignoring the /server option.
> TF14076: Cannot create the label {version} because it has child
> labels. Use /child:replace or /child:merge.
>
> at
> ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vsts.lookForErrorReturns(ProcessResult
>
>
> pr)
> at
> ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vsts.LabelSourceControl(IIntegrationResult
>
>
> result)
> at
> ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build(IIntegrationResult
> result)
> at
> ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate(IntegrationRequest
>
>
> request)
>
> If anyone has any idea why this happens in 1.5 it would be much
> appreciated.
>
> Cheers
>
> Paul
>
