| << Back to previous view |
|
[QB-171] ognl.NoSuchPropertyException: com.pmease.quickbuild.repository.PerforceModule.result
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Tom McGlynn | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
It appears that the Perforce integration is broken. This happens with PerforceRepository and TemplatedPerforceRepository. From the build log: 2006-11-22 14:44:08,812 [Thread-80] INFO - Modified client spec end. 2006-11-22 14:44:08,859 [Thread-83] INFO - Client QuickBuild.losal198.17 not changed. 2006-11-22 14:44:09,187 [Thread-87] INFO - changelist number 9753 2006-11-22 14:44:09,187 [Thread-80] ERROR - Build failed. java.lang.RuntimeException: ognl.NoSuchPropertyException: com.pmease.quickbuild.repository.PerforceModule.result at com.pmease.quickbuild.model.Configuration.evaluateBooleanExpression(Configuration.java:827) at com.pmease.quickbuild.builder.Builder.execute(Builder.java:152) at com.pmease.quickbuild.step.BuildStep.run(BuildStep.java:59) at com.pmease.quickbuild.step.Step.trigger(Step.java:179) at com.pmease.quickbuild.step.SerialStep.triggerMembers(SerialStep.java:35) at com.pmease.quickbuild.step.CompositeStep.run(CompositeStep.java:129) at com.pmease.quickbuild.step.Step.trigger(Step.java:179) at com.pmease.quickbuild.model.Configuration.performBuild(Configuration.java:1302) at com.pmease.quickbuild.model.Configuration.trigger(Configuration.java:985) at com.pmease.quickbuild.triggeringinstance.ManualTriggeringInstance.execute(ManualTriggeringInstance.java:51) at com.pmease.quickbuild.model.Queue$BuildRunner.run(Queue.java:221) at java.lang.Thread.run(Thread.java:595) Caused by: ognl.NoSuchPropertyException: com.pmease.quickbuild.repository.PerforceModule.result at ognl.ObjectPropertyAccessor.getProperty(ObjectPropertyAccessor.java:123) at ognl.OgnlRuntime.getProperty(OgnlRuntime.java:1616) at ognl.ASTProperty.getValueBody(ASTProperty.java:96) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.ASTChain.getValueBody(ASTChain.java:109) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.ASTEq.getValueBody(ASTEq.java:49) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at com.pmease.quickbuild.model.Configuration.evaluateBooleanExpression(Configuration.java:820) ... 11 more 2006-11-22 14:44:09,187 [Thread-80] INFO - Save build status as "failed". |
| Comments |
| Comment by Tom McGlynn [ 22/Nov/06 02:12 PM ] |
|
To reproduce, use a command line builder with 'cmd /c echo changelist number ${repository["perforce"].headRevision} Sorry for the blocker priority, it should probably be low. I think this is a rare occurrence. The Perforce integration works fine. I removed the OGNL from that command and put it in the version string and all worked fine. It appears I aggravated a side effect with something that was just a test, and did that as my first try with Perforce. I believe that I caused two Perforce commands to run in concurrent threads, 80 and 87, i.e. 'p4 client' and 'p4 counter change'. Perhaps they interferred with each other. |
| Comment by Robin Shen [ 22/Nov/06 10:22 PM ] |
| This has been fixed in latest 1.1.6 version. |