Chris,

I've seen this problem before.  It sounds like you're getting a null
reference because the new project isn't getting the parameter value set.
 This could happen if you somehow have a parameter defined for the first
project but not the second.  From your previous post it sounded like you
were trying to define parameters globally and pass them into all projects.
 I can't say for sure what you're experiencing without seeing your config
file(s).

On Wed, Sep 22, 2010 at 10:29 AM, Christopher <[email protected]> wrote:

> Thanks for your reply Joyce. Your suggestion worked for a while, until
> I added a second project, very similar to the first one. Building the
> new project failed with this exception:
>
> System.NullReferenceException: Object reference not set to an instance
> of an object.
>   at System.Object.GetType()
>   at
>
> ThoughtWorks.CruiseControl.Core.Tasks.DynamicValueUtility.PropertyValue.ChangePropertyValue(Object
> value)
>   at
>
> ThoughtWorks.CruiseControl.Core.Label.LabellerBase.ApplyParameters(Dictionary`2
> parameters, IEnumerable`1 parameterDefinitions)
>   at
> ThoughtWorks.CruiseControl.Core.Project.CreateLabel(IIntegrationResult
> result)
>   at
>
> ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate(IntegrationRequest
> request)
>
> I couldn't figure out why the first project worked with your
> suggestion, but the second throws an exception. I entered all the
> parameters, so they couldn't be empty. I even took a diff tool and
> compared the 2 projects line by line but none of the differences
> affected the labeller or seemed significant. I then tried installing
> the RTM version of 1.5 again to see if it might be a bug that crept
> into a later build. And get this, both projects now through this
> exception!
>
> Unless anybody knows how to fix this error, I'm going to have my
> source control block write my dynamic parameters to an XML file at the
> 'GettingModifications' stage since it doesn't seem to have any trouble
> reading the dynamic parameters, and then have my labeller read them
> from the XML file. Ugly, but it will do for now...

Reply via email to