Hendricks,
I'm a little confused about how to tell the Eventum issue that file
/foobar.php/ is the one that should be linked in the SCM Checkin
category. I was poking around in the Eventum source and found that
scm_ping.php runs process_cvs_commits.php. I've edited
process_cvs_commits.php and the login for CVSROOT, per Eventum 1.6.1
instructions, and I've also reworked the SCM admin strings in Eventum to
match the arguments of what Chora actually uses for processing diffs etc:
Erm, no. The workflow here is that you need to tweak your CVS repository
configuration so that CVS executes process_cvs_commits.php when a commit is
performed, which will in turn do a HTTP request to scm_ping.php.
The ping script is the one that will save the information to the database,
and when you load the view.php script to look at the details of an issue, it
will load that information and display the check-ins.
Does that make sense? As far as documentation goes, there are a few help
pages explaining how to set this up at the Eventum online help.
--Joao
2 messages in com.mysql.lists.eventum-usersRE: Eventum 1.6.1 vs. Chora vs. cvs