On Sat, Sep 6, 2014 at 11:21 AM, Eric Rubin-Smith <eas....@gmail.com> wrote:
> This post is a testament to Fossil's design and the ease of reading its > implementation. I've also added a Fossil patch > [...] > It requires a little hacking of the Fossil source to expose some data to > the TH1 "Transfer" hooks. But basically we can just use the > Admin->Transfers->Push and Admin->Transfers->Ticket TH1 hooks to get what > we want. Slack has a nice little HTTP API for messaging, so once the data > is in TH1 you just massage it into an appropriate HTTP call. > [...] > The issue with this is that we need to set the $uuid variable from the C > implementation prior to invoking the script. The issue is slightly > trickier for commit notifications (the Admin->Transfers->Push case), since > we can receive multiple artifacts in one Push operation. I opted to > provide a list of UUIDs to a single invocation of the script, rather than > one UUID for each of multiple invocations. This allows the script more > flexibility. (Right now the variable is called $uuid rather than e.g. > $uuidList, which is something I can fix if the devs like the general > approach.) > I am surprised this was not already available. I would use either $uuids or $uuidList to make it clear there could be more than 1 uuid. This enhancement to Fossil will certainly make integration with other tools easier, not just Slack
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
