我有两种构建配置：A 和 B。A 从 Git 存储库获取源代码，构建源代码并运行单元和集成测试，B 应该将应用程序部署到测试环境。B 在 A 上有一个“完成构建触发器”和一个“快照依赖”。A 成功运行，我希望 B 将在 A 之后启动，但我收到以下错误：
未找到构建配置的修订：A {id=bt7}，B {id=bt9} 隐藏堆栈跟踪 jetbrains.buildServer.buildTriggers.BuildTriggerException：未找到构建配置的修订：A {id=bt7}，B {id= bt9} at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.callTrigger(BuildTriggersChecker.java:37) at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.access$800(BuildTriggersChecker.java:109) at jetbrains.buildServer.serverSide.impl。 BuildTriggersChecker$BuildTriggersGroup.processTriggers(BuildTriggersChecker.java:27) at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.triggerBuilds(BuildTriggersChecker.java:94) at jetbrains.buildServer.serverSide.impl.BuildServerRunner$4.doSomething(BuildServerRunner.java:1 ) 在 jetbrains.buildServer.serverSide.impl。BuildServerRunner$BuildServerWorker.runAction(BuildServerRunner.java:12) at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.run(BuildServerRunner.java:32) at java.lang.Thread.run(Unknown Source) 原因：jetbrains。 buildServer.vcs.impl.RevisionsNotFoundException：未找到构建配置的修订：jetbrains.buildServer.vcs.impl.HistoryChangesCollector$HistoryChangesResult.checkRevisionsAreSet(HistoryChangesCollector.java:30) 处的 A {id=bt7}、B {id=bt9}在 jetbrains.buildServer.vcs.impl.HistoryChangesCollector$HistoryChangesResult.access$100(HistoryChangesCollector.java:74) 在 jetbrains.buildServer.vcs 的 jetbrains.buildServer.vcs.impl.HistoryChangesCollector$HistoryChangesResult.computeRevisions(HistoryChangesCollector.java:27)。 impl.HistoryChangesCollector$1。get(HistoryChangesCollector.java:11) at jetbrains.buildServer.vcs.impl.HistoryChangesCollector$1.get(HistoryChangesCollector.java:3) at jetbrains.buildServer.serverSide.impl.CancelableTaskHolder.waitForTaskToComplete(CancelableTaskHolder.java:9) at jetbrains。 buildServer.serverSide.impl.dependency.TopBuildDependencyGraphImpl.doCollectChanges(TopBuildDependencyGraphImpl.java:138) at jetbrains.buildServer.serverSide.impl.dependency.TopBuildDependencyGraphImpl.access$000(TopBuildDependencyGraphImpl.java:88) at jetbrains.buildServer.serverSide.impl.dependency .TopBuildDependencyGraphImpl$3.run(TopBuildDependencyGraphImpl.java) at jetbrains.buildServer.serverSide.impl.dependency.TopBuildDependencyGraphImpl$3.run(TopBuildDependencyGraphImpl.java:1) at jetbrains.buildServer.serverSide.impl.dependency。TopBuildDependencyGraphImpl$4.run(TopBuildDependencyGraphImpl.java) at jetbrains.buildServer.serverSide.impl.auth.SecurityContextImpl.runAs(SecurityContextImpl.java:24) at jetbrains.buildServer.serverSide.impl.auth.SecurityContextImpl.runAsSystem(SecurityContextImpl.java:19 ) 在 jetbrains.buildServer.serverSide.impl.dependency.TopBuildDependencyGraphImpl.collectChangesForGraph(TopBuildDependencyGraphImpl.java:8) 在 jetbrains.buildServer.serverSide 的 jetbrains.buildServer.serverSide.impl.dependency.TopBuildDependencyGraphImpl.runAsSystem(TopBuildDependencyGraphImpl.java:122)。 impl.BuildCustomizerImpl.createPromotion(BuildCustomizerImpl.java:53) 在 jetbrains.buildServer.serverSide.impl.BuildCustomizerImpl.createPromotion(BuildCustomizerImpl.java:25) 在 jetbrains.buildServer.buildTriggers.dependency。在 jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.callTrigger(BuildTriggersChecker.java:50) 的 FinishBuildTriggerService$3.triggerBuild(FinishBuildTriggerService.java:48)