On May 13, 2016, at 1:16 PM, Ron W <[email protected]> wrote:
> 
> I did not claim my scheme would work for a remote Fossil server.

The HTTP server provided by “fossil ui” is still “remote” as far as my 
questions go.  

The point is, the command line fossil client making the ci call probably didn’t 
keep the cookie it was given when it originally did the clone, and it may not 
be able to manufacture it afterward.  I did some poking around, and the 
returned cookie looks like a secure token to me, rather than something the 
client side could assemble at will.

But it turns out that it is not necessary to make the edit via HTTP.  A bit of 
playing around shows that if you close (or otherwise modify) a ticket in your 
local clone of the repo, Fossil attempts to sync the change to the remote.

You could do this before the checkin and have the ticket modification be 
autosync’d to the server, but that feels like a premature optimization.  It 
might be better to hold off modifying the local tickets until after the remote 
server accepts the checkin, then do another autosync.  More expensive, but also 
more correct.

If you don’t have permission to change the remote tickets, Fossil complains:

  Error: not authorized to write

I don’t see that as a real problem.  IMHO, it’s fine if a checkin claims to 
close a given ticket without making the checkin acceptance conditional on the 
ticket actually closing.  Someone else with the necessary permissions can later 
manually close it; you’d be no worse off than today.

> Ideally, the set of commands available to TH1 hook scripts could be expanded 
> to include things like adding/updating tags and updating tickets.

Again, I don’t see why you’d want to spend a lot of effort expanding TH1 to 
support this.  That requires every Fossil user to rebuild Fossil with TH1 hook 
support and install the custom hook.  This should be built into the core of 
Fossil.

It’s becoming a violation of expectation here in 2016 that this *doesn’t* 
happen.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to