Ticket #8 (new enhancement)

Opened 3 years ago

Last modified 3 years ago

Pull in changes automatically from somewhere to decrease lock chances

Reported by: marcel@… Owned by: moschny
Priority: minor Component: tracmtn
Version: Keywords:
Cc:

Description

Another idea perhaps to decrease locking problems?

Many trac+monotone installs probably use a cron like solution to pull revisions from a database which is used by a group of people to push to. That is, one push.db to which developers normally push their changes and a mtntrac.db which is used by the plugin in trac.

At times this causes cron errors because the db is locked. Would it be possible to have the mtn plugin pull changes in from somewhere configurable, at a configurable interval to reduce lock problems?

Attachments

Change History

Changed 3 years ago by moschny

For the plugin being able to initiate a pull it'd need to drop the automate stdio connection, because pull is currently not among the commands available for automate (which should be added anyway).

On IRC, Nathaniel suggested a  proxying daemon. This isn't a bad idea, and I might implement that as a helper for TracMonotone.

Add/Change #8 (Pull in changes automatically from somewhere to decrease lock chances)

Author


E-mail address and user name can be saved in the Preferences.


Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from moschny. Next status will be 'new'
The owner will change from moschny to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.