On Wed, May 23, 2012 at 6:01 PM, Nolan Darilek <no...@thewordnerd.info>wrote:
> I found the TH1 manual linked to in the wiki. I couldn't find a reference > for which commands Fossil includes, so I grepped through the source and > read parts of th_main.c. After doing so, it looks like TH1 won't give me > the ability to hit a URL after a repository is pushed to. If I can fetch a > URL, I can tell my Jenkins CI server that a new commit was pushed, > triggering rebuilds/redeploys. > i can't find the link, but one of the list members published (a couple years ago), a PDF book describing the TH1 API. Maybe he's listening in and can post the link for us. Another approach (non-TCL) would be to use the JSON API to poll for commits using the /json/timeline/checkin command, e.g.: http://fossil.wanderinghorse.net/repos/cson/index.cgi/json/timeline/checkin?limit=1&indent=2 Grab the last timestamp of the result (response.payload.timeline[0].timestamp) and use that as a basis for "has it changed." (Alternately, use the uuid.) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
