Greetings!
Much as we don't like the fact that some of our code is still lodged
in VSS :) , we just upgraded from 1.4.3 and started getting
exceptions with our VSS project blocks:
System.NullReferenceException: Object reference not set to an instance
of an object.
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.AppendUsernameAndPassword(PrivateArguments
builder)
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.HistoryProcessInfoArgs(DateTime
from, DateTime to, String tempOutputFileName)
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.CreateHistoryProcessInfo(IIntegrationResult
from, IIntegrationResult to, String tempOutputFileName)
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.GetModifications(IIntegrationResult
from, IIntegrationResult to, String tempOutputFileName)
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.GetModifications(IIntegrationResult
from, IIntegrationResult to)
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.FilteredSourceControl.GetModifications(IIntegrationResult
from, IIntegrationResult to)
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications(ISourceControl
sourceControl, IIntegrationResult lastBuild, IIntegrationResult
thisBuild)
at
ThoughtWorks.CruiseControl.Core.IntegrationRunner.GetModifications(IIntegrationResult
from, IIntegrationResult to)
at
ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate(IntegrationRequest
request)
Our VSS sourceControlProvider blocks, since we implemented CCNET 1.3,
have looked like this:
<sourceControlProvider type="vss" autoGetSource="true"
applyLabel="false">
<executable>C:\Program Files\Microsoft Visual
Studio\Common\VSS
\win32\ss.exe</executable>
<project>$/8.0/8.0307/NetSource</project>
<username>build</username>
<ssdir>\\antigua\shared\Documents and
Resources\Engineering
\SourceControl</ssdir>
<workingDirectory>n:\8.0\8.0307\NetSource\</workingDirectory>
<alwaysGetLatest>true</alwaysGetLatest>
<cleanCopy>true</cleanCopy>
<timeout units="minutes">60</timeout>
</sourceControlProvider>
This "build" user has no password, so we've never included the
element. However, once I added
<password></password>
to the above, everything proceeds as expected.
Wasn't sure if this is now a required element (and a documentation
update is needed), if this is a new bug (couldn't find anything on
jira), or "other".
Thanks, and kudos to the devs and community for the awesomeness that
is 1.5.
--jdavidi
