Issue Details (XML | Word | Printable)

Key: BAM-1178
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Bob Swift
Votes: 13
Watchers: 5
Operations

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

Commit quiet period

Created: 03/May/07 07:43 AM   Updated: 17/Apr/08 02:36 AM
Component/s: Build Triggers
Affects Version/s: 1.2.2
Fix Version/s: 2.0 beta 8, 2.0

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference
 

Participants: Ajay Sridhar [Atlassian], Akash Jain, Ben Mills, Bob Swift, Chris Hilton, Edwin Wong [Atlassian], Hannu Kokko and Mark Chaimungkalanont [Atlassian]
Since last comment: 25 weeks, 4 days ago
Number of comments: 12
Internal Priority: 3. Medium
Internal Work Bucket: Dependant
Labels:


 Description  « Hide
Looking at AnthillPro, they have the concept of a quite period on commits. User sets a value (say 5 minutes) for the quiet period. Build is triggered when there are commits AND a quiet period of time has passed with NO commits. This allows for a bunch of commits to be done before build is kicked of. For instance, 2 or more developers coordinating their commits. Also covers the case when a single developer "forgets" submitting something and needs to correct it quickly.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Bob Swift added a comment - 09/May/07 10:55 PM
An additional requirement (for very active projects): At most x minutes from oldest unbuilt change (don't let extended flurry of activity deter you from ever building.)

Akash Jain added a comment - 20/Jun/07 02:22 AM
I think this is pretty important, both Bob's original request and the "max minutes" comment he added. Given this isn't something we can do with a simple plug-in, I'd like to push more strongly for it. Thanks!

Ben Mills added a comment - 16/Aug/07 12:36 PM
Another vote for this functionality - first saw it in Hudson (quite useful). Thanks!

Hannu Kokko added a comment - 11/Feb/08 05:26 AM
Another vote...

Mark Chaimungkalanont [Atlassian] added a comment - 18/Mar/08 05:32 PM
Folks,

This will be available for the next beta (beta7), which will come out next Tuesday. It's implemented as an optional advanced setting for SVN.

Cheers,

Mark C


Chris Hilton added a comment - 18/Mar/08 06:05 PM
And what about other source repositories?

Mark Chaimungkalanont [Atlassian] added a comment - 18/Mar/08 06:37 PM
Chris.

Which repository do you want this for? CVS already support this. Are you after a Perforce implementation?

Cheers,

Mark C


Bob Swift added a comment - 18/Mar/08 09:06 PM
We need Perforce. This option should be repository neutral.

Chris Hilton added a comment - 18/Mar/08 10:01 PM
Oh, I didn't realize CVS already had this. Yes, Perforce would be specifically applicable for me, but I guess in general I thought this should be platform neutral, as well.

Mark Chaimungkalanont [Atlassian] added a comment - 19/Mar/08 02:48 AM
Bob & Chris,

I've added this for Perforce now. The code has been generically added but each repository may still handle the UI differently. (e.g. CVS needs the quiet period due to a lack of atomicity, so you can't disable it. For SVN & P4, the quite period is an optional advanced option)

If have a custom repository, if it implements com.atlassian.bamboo.repository.QuietPeriodAwareRepository the change detection process will take care of the rest.

Cheers,

Mark C


Bob Swift added a comment - 19/Mar/08 07:53 AM

Edwin Wong [Atlassian] added a comment - 17/Apr/08 02:36 AM
Hi guys,

This improvement is now officially released in Bamboo 2.0!

For more information about the release, check out our release notes.

You can download the latest release here today!

Regards,
Edwin