On 2/16/17, Zoltán Kócsi <[email protected]> wrote: > Is it possible to (probably yes, but how?) to trigger some external > action when a check-in happens with a particular tag?
There is not. The difficulty is in the definition of "happens". We could arrange to run a trigger on the client machine when a check-in happens. But probably you mean to run a trigger on a server when the check-in is pushed - since the server is going to be the place with the consistent environment where the script is going to run successfully. Running a script on client machines will give mixed results, depending on which client does the check-in. So maybe you could define the point where the "check-in happens" to be when the check-in is received by the server during a push. Except, that is not necessary a single point in time. A complete check-in consists of the check-in manifest artifact and all the artifacts for the individual files that changed. Those artifacts might be sent over the same push operation (and they usual are) but there is no guarantee of that. The server might receive the manifest now and some of the content files several hours later. At which point is the trigger run? All that said, I think some people might have worked out a trigger system using TH1, but I have not kept up with the details of that so they will need to brief you. > > For example, if we have a project of which the docs are generated using > Doxygen and we want to keep the docs of the latest release on the > server as a publicly available HTML tree, then it would be good if a > check-in with the tag 'release' or something akin could trigger an > external script, which checks out that release, runs Doxygen on it and > installs the result on the web server. > > Or, if we want to provide the latest stable version as binary, Fossil > could trigger the whole compilation process with a tagged check-in as > above and install the binaries in the downloadable files directory of > the webserver. > > I'm almost certain that Fossil can do that, but I couldn't find it in > the docs. Any help or pointers to the relevant docs would be most > appreciated. > > Thanks, > > Zoltan > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
