Talk:SCMMigrationTasks

From Genunix

Tools Putback

stability of ARC information

The ARC case information is available as a CSV snapshot. The checking tools (particularly the comment checker) can access information about individual cases using the onbld.Checks.DbLookups class, which invokes a CGI script on the server. The CGI script reads the CSV file and returns information about the specified case.

The Tonic team owns the CGI script and onbld.Checks.DbLookups. The ARC folks own the CSV file.

The location and format of the CSV file should be considered Committed, but the update frequency should be considered Volatile. We can expect a major release of the ARC tools at some point, but we can work with the ARC team to deal with the transition. Details at http://mail.opensolaris.org/pipermail/scm-migration-dev/2008-February/001513.html.

intermittent failure to load scmhooks.hg

• Why would failure to read the configuration file be intermittent? I can reliably reproduce the error when I pull from oss-app2. So the intermittent errors would be from when requests get sent to app2, rather than app1. The errors are because /home/anon/etc/tonic/common.ini is owned by root:root on app2. From looking at app1, it should be owned by anon:scm.

• What are the implications of failure to load our extensions?
  • Auditing and access control, as provided by the SCM, are important considerations for Solaris's security rating.
    • Access control needs to be failsafe (i.e., disallow updates). And testing shows that to be the case. If the pretxnchangegroup hook fails to load, Mercurial (0.9.3) aborts the push.
    • The situation with respect to auditing is more complicated. We have two main audit mechanisms: notification emails (via the changegroup hook) and "hg log". If the changegroup hook fails to load, we lose some information about who pushed what when, but the actual changegroups can still be audited using "hg log". And because "hg log" shows the changesets in linear order, we can use successful notification emails to bound the changesets that would have to be examined due to a failure of the changegroup hook. See also CR 6664127.