It's all about the answers!

Ask a question

RTC continuous integration builds sometimes persist after failure


Spencer Murata (2.3k115870) | asked Sep 18 '12, 11:27 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
 I have RTC integrated with Build Forge and I am running continuous integration builds between the two.  However intermittently I see a failed build in RTC, but the matching build in Build Forge is purged, meaning the build should not have run.  I see the following error in the log related to this build when I turn on the log4j debug for the Build Forge integration:

2012-08-08 12:56:11,870 [ ccm: AsynchronousTaskRunner-4] DEBUG .team.internal.service.BuildForgeBuildLoopRunnable  - CRJAZ0223I The following item has been changed by another operation:
Input: com.ibm.team.build.internal.common.model.impl.BuildRequestImpl@7df07df0 (stateId: [UUID _9TAg0OF5EeG91uKzI7pnSg], itemId: [UUID _7R6y0OF5EeG91uKzI7pnSg], origin: <unset>, immutable: true) (contextId: [UUID _-H1S1L8FEeG2ivdBPCt9xQ], modified: 2012-08-08 12:56:11.869, workingCopy: <unset>) (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: [UUID _9Fg3YOF5EeG91uKzI7pnSg]) (processed: true, created: 2012-08-08 12:55:58.333)

Current: com.ibm.team.build.internal.common.model.impl.BuildRequestImpl@146e146e (stateId: [UUID _9R8J0OF5EeG91uKzI7pnSg], itemId: [UUID _7R6y0OF5EeG91uKzI7pnSg], origin: <unset>, immutable: true) (contextId: [UUID _-H1S1L8FEeG2ivdBPCt9xQ], modified: 2012-08-08 12:56:11.757, workingCopy: <unset>) (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: [UUID _9Fg3YOF5EeG91uKzI7pnSg]) (processed: true, created: 2012-08-08 12:55:58.333)

What is happening here?  How can I fix it?

Accepted answer


permanent link
Spencer Murata (2.3k115870) | answered Sep 18 '12, 11:28 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
 This is a known defect being tracked under work item 222056.  The problem is with how the included environments in the Build Forge environment are handled.  To work around this problem, move the included environments in Build Forge at the top level (the level assigned to the project) to the top of the environment.  This will cause them to be executed first in the integration and will bypass the problem.
Spencer Murata selected this answer as the correct answer

Your answer


Register or to post your answer.