Issue Details (XML | Word | Printable)

Key: BAM-747
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Keith Johnston
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Bamboo

Perforce repository polling build plan not building

Created: 22/Jan/07 02:16 PM   Updated: 20/Apr/07 01:33 AM
Component/s: Build Triggers
Affects Version/s: 1.0-beta
Fix Version/s: 1.0.4

Time Tracking:
Original Estimate: 4 hours
Original Estimate - 4 hours
Remaining Estimate: 4 hours
Remaining Estimate - 4 hours
Time Spent: Not Specified
Remaining Estimate - 4 hours

Internal Priority: 3. Medium
Participants: Brydie McCoy [Atlassian], Edwin Wong [Atlassian], Keith Johnston and Mark Chaimungkalanont [Atlassian]
Since last comment: 1 year, 21 weeks, 2 days ago
Internal Work Bucket: Investigating
Number of comments: 4
Labels:


 Description  « Hide
I created a build plan in a project that already had a manual build. I set the type of this new build to 'Poll repository for changes' every 60 seconds. I see in the activity log that the polling is happening and that the changes are being synced - but the build is not occurring.

22-Jan-2007 14:03:58 Generating build results summary...
22-Jan-2007 14:03:58 Indexing build results...
22-Jan-2007 14:03:58 Finished saving build CONNECT3-DELTA-2
22-Jan-2007 14:03:59 //buildtest_DEVINT2/​buildtest/​... - file(s) up-to-date.
22-Jan-2007 14:04:00 Sending build results email for build:Connect 4 Three - Delta build:2
22-Jan-2007 14:04:59 //depot/​userbranches/​kjohnston_main_user/​buildtest/​connectfour/​ build.xml#3 - updating D:\p4\​buildtest\​connectfour\​build.xml
22-Jan-2007 14:06:00 //buildtest_DEVINT2/​buildtest/​... - file(s) up-to-date.
22-Jan-2007 14:07:00 //buildtest_DEVINT2/​buildtest/​... - file(s) up-to-date.
22-Jan-2007 14:08:01 //buildtest_DEVINT2/​buildtest/​... - file(s) up-to-date.
22-Jan-2007 14:09:01 //buildtest_DEVINT2/​buildtest/​... - file(s) up-to-date.
22-Jan-2007 14:10:02 //depot/​userbranches/​kjohnston_main_user/​buildtest/​connectfour/​ build.xml#4 - updating D:\p4\​buildtest\​connectfour\​build.xml
22-Jan-2007 14:11:03 //buildtest_DEVINT2/​buildtest/​... - file(s) up-to-date.
22-Jan-2007 14:12:03 //buildtest_DEVINT2/​buildtest/​... - file(s) up-to-date.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Keith Johnston added a comment - 22/Jan/07 02:23 PM
This could be the source of the problem - when I create the delta build plan, I get the error below. I created the plan by cloning the manual build plan I already had. I'll try creating one without cloning.

org.springframework.dao.DataIntegrityViolationException: Hibernate operation: could not insert: com.atlassian.bamboo.labels.LabelImpl#229377; SQL []; Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_245 in statement [insert into LABEL (NAME, NAMESPACE, CREATED_DATE, UPDATED_DATE, LABEL_ID) values (?, ?, ?, ?, ?)]; nested exception is java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_245 in statement [insert into LABEL (NAME, NAMESPACE, CREATED_DATE, UPDATED_DATE, LABEL_ID) values (?, ?, ?, ?, ?)]
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_245 in statement [insert into LABEL (NAME, NAMESPACE, CREATED_DATE, UPDATED_DATE, LABEL_ID) values (?, ?, ?, ?, ?)]
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
at net.sf.hibernate.impl.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:22)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:462)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:436)
at net.sf.hibernate.impl.ScheduledInsertion.execute(ScheduledInsertion.java:37)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2449)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2435)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2392)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2261)
at net.sf.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:61)
at org.springframework.orm.hibernate.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:490)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:500)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:473)
at org.springframework.transaction.interceptor.TransactionAspectSupport.doCommitTransactionAfterReturning(TransactionAspectSupport.java:267)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
at $Proxy15.addLabel(Unknown Source)
at com.atlassian.bamboo.labels.AutoLabelBuildCompleteAction.run(AutoLabelBuildCompleteAction.java:41)
at com.atlassian.bamboo.event.BuildCompleteNotifier.performCustomBuildCompleteAction(BuildCompleteNotifier.java:104)
at com.atlassian.bamboo.event.BuildCompleteNotifier.doTask(BuildCompleteNotifier.java:70)
at com.atlassian.bamboo.container.BambooTask.run(BambooTask.java:33)
at java.lang.Thread.run(Unknown Source)


Keith Johnston added a comment - 22/Jan/07 03:29 PM
OK - I deleted all my builds and re-created them from scratch. I think the hibernate errors were due to my importing of a past configuration after upgrading to beta2.

I still have the same problem - this time with no hibernate errors. I see in the activity log that it syncs the file that changed (a build.xml file), but it did not rebuild.


Keith Johnston added a comment - 22/Jan/07 03:30 PM
Should have said after upgrading to beta1 from 0.9.

Brydie McCoy [Atlassian] added a comment - 13/Apr/07 02:30 AM
Hi Keith,

Sorry I missed this issue, it must have slipped through the cracks.

Good news though, we have found the cause of this problem. Bamboo used a timstamp to decide it if will build, however, if the bamboo clock and perforce clock are out of sync then it can cause the above problem.

I have changed the way Bamboo detects changes to use the change list number rather than the timestamp. This was part of release 1.0.4 (released yesterday). So upgrading should solve your problems.

There were also several other perforce fixes released with 1.0.4 that you might be interested in. You can find details here: http://confluence.atlassian.com/display/BAMBOO/Bamboo+1.0.4+Release+Notes.

Cheers
Brydie