New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: BAM-871
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Keith Johnston
Votes: 0
Watchers: 1
Operations

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

Manual builds still poll the perforce server

Created: 14/Feb/07 04:52 PM   Updated: 01/Apr/07 09:49 PM
Component/s: Build Process
Affects Version/s: 1.0-rc2
Fix Version/s: 1.0.4

Time Tracking:
Not Specified

Participants: Brydie McCoy [Atlassian], Edwin Wong [Atlassian], Keith Johnston and Nick Sieger
Since last comment: 1 year, 21 weeks, 4 days ago
Number of comments: 4
Labels:


 Description  « Hide
I only noticed this because our Perforce server was down earlier today. The log filled up with errors and the builds were all disabled. Apparently even manually triggered builds are polling the source code repository. Doesn't seem like they would need to.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Nick Sieger added a comment - 23/Mar/07 10:01 AM
Is it possible that this is happening for other repo types as well? My build server is pulling code from an open source SVN repo on rubyforge.org, but it appears they have some sort of DOS detection because Bamboo repeatedly spits out these messages: 
23-Mar-2007 07:09:21  	 Failed to get the build source code:ActiveRecord-JDBC - Trunk
23-Mar-2007 07:09:22 	Manual build request, checking for source code changes
23-Mar-2007 07:09:22 	Failed to get the build source code:ActiveRecord-JDBC - Trunk
23-Mar-2007 07:09:23 	Manual build request, checking for source code changes

And here's a log snippet:

2007-03-23 07:09:35,621 ERROR [BAM::BuildChangeDetector] [DefaultBuildChangeDetector] Failed to get the build source code
com.atlassian.bamboo.repository.RepositoryException: ActiveRecord-JDBC - Trunk
	at com.atlassian.bamboo.repository.svn.SvnRepository.getChangesSinceLastBuild(SvnRepository.java:376)
	at com.atlassian.bamboo.build.strategy.AbstractBuildStrategy.populateChangeList(AbstractBuildStrategy.java:92)
	at com.atlassian.bamboo.build.strategy.ManualBuild.requiresBuild(ManualBuild.java:40)
	at com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166)
	at com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114)
	at com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77)
	at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34)
	at java.lang.Thread.run(Thread.java:595)
Caused by: org.tmatesoft.svn.core.SVNException: svn: 210002: Network connection closed unexpectedly
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:48)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readChar(SVNReader.java:546)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:258)
	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:206)
	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.handshake(SVNConnection.java:76)
	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:61)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:970)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:112)
	at com.atlassian.bamboo.repository.svn.SvnRepository.getChangesSinceLastBuild(SvnRepository.java:327)
	... 7 more

[ Permlink | « Hide ]
Edwin Wong [Atlassian] added a comment - 30/Mar/07 02:27 AM
Guys,

Sorry the delayed response about this one. We are still investigating the different connection errors that are happening.

Keith - regarding the Perforce polling for manual builds - this is something we have noticed and are getting fixed so that it does not constantly poll the Perforce repo. Please see BAM-1078.

Nick - no, this is a slightly different issue with Subversion. From the looks fo things, it seems that your subversion ran into some network error while trying to perform a code update.
Is this still happnening? If so, can you checkout and update the same source code on the Bamboo box using a different subversion client?

Cheers,
Edwin


[ Permlink | « Hide ]
Nick Sieger added a comment - 30/Mar/07 09:25 AM
Edwin – I upgraded to 1.0.3 and for the moment subversion seems to be working again. To answer your question, I was able to check out the same source code with command-line svn, in fact I have other builds running on the same box that do an svn export of that code as part of the build of a different component. If I start seeing the behavior again I'll open a new issue. Thanks!

[ Permlink | « Hide ]
Brydie McCoy [Atlassian] added a comment - 01/Apr/07 09:48 PM
Hi Keith,

The frequency of the polling was because Bamboo was retrieving the client root from perforce which it then uses to determine if the plan needs building. As of 1.0.4 the client root will be cached to remove the excessive polling.

However, since the client root is now being cached, if you change the root in Perforce, Bamboo will require a restart to pick up this change. There is an issue raised for this if you wish to track it (BAM-1082).

Cheers
Brydie
Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13_beta1-#328) - Bug/feature request - Atlassian news - Contact Administrators