Hi Robert, I went over the patch.
On Thu, 2007-01-18 at 09:28 -0800, Robert Hudson wrote:
> > Was an extra "activity" issued ? When was it issued ?
>
> Yes, I created a new activity, hopefully the help file I posted will
> clarify?
It seems that this capability could be implemented on activity_commit as
an additional policy. E.g. add in glue.conf a policy configuration
variable that stores the commands that should be executed on the server
after a successful commit.
> > If there is a generalization that could be derived from this
> > work, then definitely I'd be willing to merge it.
>
> Hope that I've managed to make it fairly general.
I had a look over your text document. It seems that you want to execute
the tool describe (that issued the activity) every time you commit. This
is because you assume all your documents are PDF files. Perhaps this
could be further generalized to provide regular expressions that given a
match will execute a program on the daemon server (which in your case
would be '.*pdf'.
This could be further generalized to execute a program on the repository
server (where the hooks are executed) -- but that's what the hooks
mechanism of an SCM system is for really. The benefit, however, would be
that general information would have already been decoded from the SCM
(e.g. branch name, revision number, affected files, etc) so that Scmbug
could be the vehicle for supplying the required arguments to such tools.
Think of something like:
policy_execute_binaries => {
enabled => 1,
values => {
'.*pdf' => { execute_on_daemon => 1,
binary => '/usr/local/scripts/my_pdf_script.sh'
}
}
}
The first question that comes to mind is do we need to supply arguments
to that script ? What does your script do right now, precisely ?
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
