Problem with NuGet Dependency Trigger

Hi Everyone,
We are using TeamCity Professional 8.0.6 (build 27767) and we have a project that publishes nuget packages to our own private nuget repository. We have another project that has a NuGet Dependency Trigger that listens to that nuget repository. We recently change the default nuget version to 2.8 and since then the project that depends on the nuget repository has been getting this error:

Problem with NuGet Dependency Trigger.
Failed to check for package versions. Value cannot be null.
Parameter name: property

Hide stacktrace

jetbrains.buildServer.buildTriggers.BuildTriggerException: Failed to check for package versions. Value cannot be null.
Parameter name: property
at jetbrains.buildServer.nuget.server.trigger.NamedPackagesUpdateChecker.checkChanges(NamedPackagesUpdateChecker.java:66)
at jetbrains.buildServer.nuget.server.trigger.NuGetSimpleTrigger$1.triggerBuild(NuGetSimpleTrigger.java:100)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker$4.run(BuildTriggersChecker.java:1)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:103)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.callTrigger(BuildTriggersChecker.java:109)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.access$800(BuildTriggersChecker.java:57)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker$BuildTriggersGroup.processTriggers(BuildTriggersChecker.java:11)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.triggerBuilds(BuildTriggersChecker.java:9)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$4.doSomething(BuildServerRunner.java:1)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.runAction(BuildServerRunner.java:17)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.run(BuildServerRunner.java:16)
at java.lang.Thread.run(Unknown Source)

Is anyone else having this issue? Do I just need to revert back to using NuGet 2.7?

Thanks,

Please sign in to leave a comment.