Maven snapshot dependency trigger in Team City 7 (BuildTriggerException)

I was attempting to get the Maven snapshot dependency trigger working for a project when i got this exception.

Couldn't perform check for SNAPSHOT dependencies update because there was an error reading POM. See Maven tab for details
« Hide stacktrace
jetbrains.buildServer.buildTriggers.BuildTriggerException: Couldn't perform check for SNAPSHOT dependencies update because there was an error reading POM. See Maven tab for details
at jetbrains.buildServer.buildTriggers.async.impl.AsyncPolledBuildTrigger.checkJobStatus(AsyncPolledBuildTrigger.java:100)
at jetbrains.buildServer.buildTriggers.async.impl.AsyncPolledBuildTrigger.triggerBuild(AsyncPolledBuildTrigger.java:48)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.triggerBuilds(BuildTriggersChecker.java:4)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$4.doSomething(BuildServerRunner.java:2)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.run(BuildServerRunner.java:26)
at java.lang.Thread.run(Unknown Source)
Caused by: jetbrains.buildServer.buildTriggers.async.CheckJobCreationException: Couldn't perform check for SNAPSHOT dependencies update because there was an error reading POM. See Maven tab for details
at jetbrains.buildServer.maven.trigger.SnapshotsCheckJob.<init>(SnapshotsCheckJob.java:70)
at jetbrains.buildServer.maven.trigger.MavenSnapshotDependencyTriggerService$1.createJob(MavenSnapshotDependencyTriggerService.java:40)
at jetbrains.buildServer.buildTriggers.async.impl.AsyncPolledBuildTrigger.checkJobStatus(AsyncPolledBuildTrigger.java:90)
... 5 more
Caused by: jetbrains.buildServer.maven.metadata.MavenMetadataNotAvailableException
at jetbrains.buildServer.maven.metadata.impl.MavenMetadataBean.getActualMavenProject(MavenMetadataBean.java:79)
at jetbrains.buildServer.maven.trigger.SnapshotsCheckJob.<init>(SnapshotsCheckJob.java:45)
... 7 more


The documentation page (http://confluence.jetbrains.net/display/TCD7/Configuring+Maven+Triggers) is a bit sparse on information.  The stacktrace indicates that Team City is looks for some information in the pom that just isn't there.. Any ideas? The parent pom is inherited from another Maven artefact published to an in-house Maven repository defined in ~/.m2/settings.xml.

1 comment
Comment actions Permalink

Hello Kim,
Sorry for the delay.

Do you still have the issue?
Please open Maven tab on project overview page: can you see information about your maven build? Is there an error message?

0

Please sign in to leave a comment.