'Problem with VCS Trigger' Cannot find a node
We recently updated to TC 2025.03 (build 186049) and I'm assuming that is related to an error with a specific project's VCS trigger that has cropped up. I'm not spotting any obvious server logs that give more information, but the stack trace is bubbled up to the UI (included below).
The VCS root itself is connecting fine. The trigger is provided by a template that other projects also use and aren't having the same issue. The main difference between them is the Branch filter pulls from a project param, but nothing has changed with its value lately that i can spot.
jetbrains.buildServer.buildTriggers.BuildTriggerException: Cannot find a node: 134674
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.wrapInBuildTriggerException(BuildTriggersChecker.java:48)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.doActivateTrigger(BuildTriggersChecker.java:157)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.activateTrigger(BuildTriggersChecker.java:159)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker$BuildTriggersGroup.processTriggers(BuildTriggersChecker.java:17)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.lambda$null$5(BuildTriggersChecker.java:215)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.lambda$processTriggersOfTypes$6(BuildTriggersChecker.java:64)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.IllegalArgumentException: Cannot find a node: 134674
at jetbrains.buildServer.util.graph.DAG.ensureContainsNode(DAG.java:260)
at jetbrains.buildServer.util.graph.BaseModificationDAG.reverseBreadthFirstSearch(BaseModificationDAG.java:177)
at jetbrains.buildServer.util.graph.WrappedDAG.reverseBreadthFirstSearch(WrappedDAG.java:91)
at jetbrains.buildServer.util.graph.WrappedDAG.reverseBreadthFirstSearch(WrappedDAG.java:17)
at jetbrains.buildServer.serverSide.impl.FindPromotionStrategyFactory$ExactRevisionMatchStrategy.findBuildContainingChange(FindPromotionStrategyFactory.java:21)
at jetbrains.buildServer.serverSide.impl.FindPromotionStrategyFactory$ExactRevisionMatchStrategy.forModification(FindPromotionStrategyFactory.java:8)
at jetbrains.buildServer.serverSide.impl.FindPromotionStrategyFactory$MixedVcsRootTypesStrategy.forModification(FindPromotionStrategyFactory.java:3)
at jetbrains.buildServer.serverSide.impl.ChangesCalculatorDagVisitor.discover(ChangesCalculatorDagVisitor.java:70)
at jetbrains.buildServer.serverSide.impl.ChangesCalculatorDagVisitor.discover(ChangesCalculatorDagVisitor.java:52)
at jetbrains.buildServer.util.graph.ChildrenFirstSearch.visit(ChildrenFirstSearch.java:61)
at jetbrains.buildServer.util.graph.ChildrenFirstSearch.run(ChildrenFirstSearch.java:55)
at jetbrains.buildServer.util.graph.VcsDAGs.childrenFirstSearch(VcsDAGs.java:144)
at jetbrains.buildServer.serverSide.impl.changeProviders.BasicDagBasedChangesProvider.lambda$getChanges$0(BasicDagBasedChangesProvider.java:35)
at jetbrains.buildServer.serverSide.impl.query.VcsChangesGraphQuery$VcsRootDAG.withConnectedDAG(VcsChangesGraphQuery.java:27)
at jetbrains.buildServer.serverSide.impl.query.VcsChangesGraphQuery.withVcsRootModificationIdDAG(VcsChangesGraphQuery.java:50)
at jetbrains.buildServer.vcs.impl.VcsRootInstanceImpl.withConnectedDAG(VcsRootInstanceImpl.java:283)
at jetbrains.buildServer.serverSide.impl.changeProviders.BasicDagBasedChangesProvider.getChanges(BasicDagBasedChangesProvider.java:34)
at jetbrains.buildServer.serverSide.impl.changeProviders.DagBasedChangesProvider.getChanges(DagBasedChangesProvider.java:8)
at jetbrains.buildServer.serverSide.impl.changeProviders.CompositeChangesProvider.getChanges(CompositeChangesProvider.java:3)
at jetbrains.buildServer.serverSide.impl.BuildVcsChangesCalculatorImpl.calculate(BuildVcsChangesCalculatorImpl.java:139)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.lambda$calculateVcsChanges$13(AbstractBuildPromotion.java:443)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.calculateVcsChanges(AbstractBuildPromotion.java:188)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.getOwnChanges(AbstractBuildPromotion.java:552)
at jetbrains.buildServer.serverSide.impl.DummyBuildPromotion.getOwnChanges(DummyBuildPromotion.java:235)
at jetbrains.buildServer.serverSide.impl.DummyBuildPromotion.getOwnChanges(DummyBuildPromotion.java:275)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion$VcsChangesProvider.addDetectedChanges(AbstractBuildPromotion.java:23)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.fillDetectedChanges(AbstractBuildPromotion.java:467)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.getDetectedChanges(AbstractBuildPromotion.java:172)
at jetbrains.buildServer.serverSide.impl.BuildTypeBranchImpl.getDetectedChanges(BuildTypeBranchImpl.java:65)
at jetbrains.buildServer.buildTriggers.vcs.BranchChangesCalculator.getChanges(BranchChangesCalculator.java:12)
at jetbrains.buildServer.buildTriggers.vcs.SingleBranchVcsTrigger.triggerActivated(SingleBranchVcsTrigger.java:169)
at jetbrains.buildServer.buildTriggers.vcs.AllBranchesVcsTrigger.triggerActivated(AllBranchesVcsTrigger.java:20)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.doActivateTrigger(BuildTriggersChecker.java:502)Please sign in to leave a comment.
I think I got this fixed, but i'm not positive what the solution was. I noticed that the triggers log was being spammed constantly with:
Initializing the VCS trigger state for 1532 branches
and the repo being monitored has had 1532 PRs open since the dawn of time. I added the pull request feature, messed with the branchspec and branch trigger rules and something in there caused it to instead only see the 4 open PRs and then start triggering on updates as expected. I think the most likely culprit was that the branch spec had this (and the `pull/*` was the issue):
Could you let me know what is your current branch specification that resolved the issue?
Best regards,
Anton
I dropped line one from the above so now i just have this
+:refs/heads/(develop)
The pull/* was probably never needed, but before we updated to 2025.03 it also didn't seem to be an issue. This update has had a few oddities with VCS triggering; we had another config requeue seemingly every PR/merge build that the vcs root has ever seen come through
Thanks! It looks like it indeed picked up all PRs.
By the way, from what version have you updated? There may have been some changes in the PR build feature or similar.
Best regards,
Anton
From the TC update log i believe the prior version was 2024.12.3
Thank you so much for taking the time to answer these questions!
This may help in the future if someone will encounter similar symptoms.
Thanks,
Anton