ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Option to force repository update (Feature #923)

Added by Yehuda Katz at 2012-03-07 01:35 am. Updated at 2012-03-07 05:25 pm.

Status:Open Start date:2012-03-07
Priority:Normal Due date:
Assignee:- % Done:


Target version:-
Remote issue URL: Affected version:


Users with manager privilege should be able to force a full repository update (the same as calling /sys/fetch_changesets) with a link on the repository page.
I am not sure how complicated that would be.

Associated revisions

Revision 6331809b
Added by Jean-Philippe Lang at 2008-03-27 08:27 pm

Translation updates: (closes #915, #927, #929, #923, #914, #919)
  • Japanese (Satoru Kurashiki)
  • Simplified Chinese (chaoqun zou)
  • Danish (kim madsen)
  • Norwegian (Kai Olav Fredriksen)
  • Traditional Chinese (shortie lo)
  • German (Sven Schuchmann)

git-svn-id: e93f8b46-1217-0410-a6f0-8f06a7374b81


Updated by Felix Schäfer at 2012-03-07 05:16 pm

Depending on what you call a "full" repo update, this already exists, albeit not as a button.

The fetch_changesets functions is called every time any user opens any repository page in the project if the "auto-update" feature is checked in the global administration (which IIRC it is by default).

Updated by Yehuda Katz at 2012-03-07 05:25 pm

I had "auto-update" checked, but for some reason the repository was not being updated.
I have one SVN and two GIT repositories and none were being updated unless I called the /sys/fetch_changesets url directly (I added it to my SVN post commit hooks, but I can't get every developer to do that).

Also available in: Atom PDF