Issue Details (XML | Word | Printable)

Key: BAM-960
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Ben Walding
Votes: 1
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

Builds tend to disable themselves far too frequently

Created: 03/Mar/07 07:03 PM   Updated: 04/Jun/07 01:36 AM
Component/s: Administration (General)
Affects Version/s: 1.0
Fix Version/s: 1.0.2

Time Tracking:
Not Specified

Participants: Ajay Sridhar [Atlassian], Ben Walding, Mark Chaimungkalanont [Atlassian] and Mark Gaylard
Since last comment: 1 year, 25 weeks, 6 days ago
Number of comments: 5
Labels:


 Description  « Hide
(I've only tagged this as "Major" as it's majorly annoying! - there is a manual workaround)

Our main Codehaus instance (and test instances) all suffer from unreliable connections back to the SVN servers (as they are countries apart I suspect).

Whenever there is a timeout for N periods, the build is disabled. However disabling the build is not really required - it should just wait until the server is available again (perhaps with some kind of backoff algorithm.

So if there is any network outage, all my build plans are disabled - 15 odd at the moment, more in the future. That's a lot of clicking to get everything going again, and I have to notice first.

Thanks,

Ben



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mark Chaimungkalanont [Atlassian] added a comment - 04/Mar/07 03:38 AM
Ben,

Some other people also have had problems with this feature. We have had some debate whether to just remove it completely. Do you reckon that'd be okay for you?

Cheers,

Mark C


Ben Walding added a comment - 04/Mar/07 06:28 AM
I think disabling this would be useful for Codehaus.

However I think some visual or other notification that the build has been unable to run for a period of time would also be useful.

The rationale:

If the build is running successfully I won't receive emails.
If the build can't check out, then I'd like to know occasionally - eg. after a day (a tradeoff between notifying too frequently and not early enough).

The build should probably also be highlighted ("This build hasn't been able to connect to the source code repository for X days" in dayglo orange text)

(I'm clearly not a graphic designer!)


Mark Gaylard added a comment - 05/Mar/07 06:43 PM
+1 for disabling feature, but agree some sort of other notification would be nice

Mark Chaimungkalanont [Atlassian] added a comment - 12/Mar/07 08:30 PM
Guys,

This is now partially done for 1.0.2 (we've disabled it)

We're building a more robust notification scheme in the background at the moment, so maybe the real fix for this will come after that.

Cheers,

Mark C


Ajay Sridhar [Atlassian] added a comment - 04/Jun/07 01:36 AM
Hi Guys,

I will resolve this issue as builds no longer disable themselves (post 1.0.2) and this should no longer be an issue.

Cheers,
Ajay