I am seeing errors on the console related to using tickets. It does not appear to be affecting the builds, however the users are getting confused as they think there is an error.
I have enclosed the stack trace.
The file does exist, all pipelines will use the same ticket.
Is it a race condition resulting from all the pipleines continuously polling the source depot?
Stack Trace
2011-12-15 14:27:27,546 WARN [MessageListener for MaterialUpdateListener] MaterialDatabaseUpdater:91 - [Material Update] Modification check failed for material:
java.lang.RuntimeException: Error performing command: --- Command ---
p4 login
--- Environment ---
{P4PORT=, P4CLIENT= , P4USER= }
--- INPUT ----
******
--OUTPUT ---
Enter password:
--- ERROR ---
ERROR: Fatal client error; disconnecting!
ERROR: chmod: C:\Documents and Settings\username\p4tickets.txt: The system cannot find the file specified.
ERROR:
ERROR:
---
at com.thoughtworks.cruise.util.ExceptionUtils.bomb(ExceptionUtils.java:24)
at com.thoughtworks.cruise.config.materials.perforce.P4Material.getP4(P4Material.java:137)
at com.thoughtworks.cruise.config.materials.perforce.P4Material.modificationsSince(P4Material.java:111)
at com.thoughtworks.cruise.server.materials.ScmMaterialUpdater.insertLatestOrNewModifications(ScmMaterialUpdater.java:26)
at com.thoughtworks.cruise.server.materials.MaterialDatabaseUpdater.insertLatestOrNewModifications(MaterialDatabaseUpdater.java:121)
at com.thoughtworks.cruise.server.materials.MaterialDatabaseUpdater.updateMaterialWithNewRevisions(MaterialDatabaseUpdater.java:113)
at com.thoughtworks.cruise.server.materials.MaterialDatabaseUpdater$2.doInTransaction(MaterialDatabaseUpdater.java:81)
at com.thoughtworks.cruise.server.transaction.TransactionCallback.doWithExceptionHandling(TransactionCallback.java:8)
at com.thoughtworks.cruise.server.transaction.TransactionTemplate$2.doInTransaction(TransactionTemplate.java:37)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
at com.thoughtworks.cruise.server.transaction.TransactionTemplate.executeWithExceptionHandling(TransactionTemplate.java:33)
at com.thoughtworks.cruise.server.materials.MaterialDatabaseUpdater.updateMaterial(MaterialDatabaseUpdater.java:79)
at com.thoughtworks.cruise.server.materials.MaterialUpdateListener.onMessage(MaterialUpdateListener.java:27)
at com.thoughtworks.cruise.server.materials.MaterialUpdateListener.onMessage(MaterialUpdateListener.java:12)
at com.thoughtworks.cruise.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:46)
at com.thoughtworks.cruise.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:31)
at java.lang.Thread.run(Thread.java:619)
Unable to find p4tickets file
Comments
1 comment
I am still getting Modification check failures for all my pipleines which have Perforce Materials. The problem seems to be the p4tickets.txt file is unable to be read. I believe there may be a race condition since all the pipleines are executed by the same user and this file is in the same location for all. The file is indeed present when I verify the error. This error is more an annoyance, as it is not really an error at all. However, it does result in having to verify the error whenever it is displayed in the interface. Is this an issue with selecting the "Use tickets" checkbox? Is it possible to set the perforce user and password for ALL pipelines in one location, which cannot be overridden? It seems erdundant to have to specify it for each material definition.
Please sign in to leave a comment.