Modify

Opened 12 years ago

Last modified 12 years ago

#8 new enhancement

Pull in changes automatically from somewhere to decrease lock chances

Reported by: marcel@… Owned by: Thomas 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 (0)

Change History (1)

comment:1 Changed 12 years ago by Thomas 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.

Last edited 5 years ago by Thomas Moschny (previous) (diff)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain Thomas Moschny.
as The resolution will be set.
to The owner will be changed from Thomas Moschny to the specified user.
The owner will be changed from Thomas Moschny to anonymous.

Add Comment


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

 
Note: See TracTickets for help on using tickets.