On Tue, September 14, 2010 at 6:06 pm, DRH wrote: > On Tue, Sep 14, 2010 at 12:50 PM, Yusuf X <[email protected]> wrote: > >> Hi, I have a need to build a repository once it's checked in. A handy >> feature would be to trigger a script (i.e., "ant build_repo1.xml") >> once code is pushed to the server for a particular repository. It >> should not be a large change; if it's not in, shall I add it? >> > > Additional information about the Fossil sync protocol is here: > > http://www.fossil-scm.org/fossil/doc/tip/www/sync.wiki > > You can get a better idea of how sync works by reading the "Overview" > section. With that in mind: > > How does the repository know when "code" has been pushed, versus (say) > wiki > modifications or new tickets or other artifacts? > > What if two or more code changes are pushed at once? > > When a "push" occurs, the client makes multiple round-trip requests to the > server, pushing a number of artifacts on each push. Just to keep the size > of HTTP manageable, the client will split a "push" up into multiple > round-trips if there are multiple files that have changed and the change > sets (which are a binary xdelta) exceeds a size threshold. Does the > callback > get invoked on each partial update? Or does it wait until the complete > update is received? How does the server know when the update is complete? >
May I add my own little dose of pessimism? There _will_ be portability issues. It is easy to forget that Fossil is distributed isn't it? Even if a repository knows what to do and how to do it, how does it know it is the repository that is supposed to do it? For checkins on what branches? How does it get out of its chroot jail? What does it do if whatever it runs returns an error? I am not saying that what is asked for is unreasonable, just that it is not a job for Fossil itself. Fossil should do what it does. If you want something different for your developers/contributors, write a wrapper application. If you want something done on a repository server, write an independent program that reads the repository database at intervals - scheduled or a polling daemon. Just my opinion of course. Bets Wishes, Eric _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
