This is way not something we need to worry about now, but chx brought this up in the meta issue, and I'm a big stickler for documentation. ;)
From grepping through, it looks like there are a quite a few places where the testbot code makes hard-coded assumptions about cvs. Should be pretty trivial to update them, though. Tagging as Novice. :)
The two modules to keep an eye on are http://drupal.org/project/project_issue_file_test (server, runs on qa.drupal.org and manages the queue of patches) and http://drupal.org/project/project_issue_file_review (client, runs on drupal.org and pushes results to the issue queue).
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | git-post-commit.txt | 738 bytes | deekayen |
Comments
Comment #1
marvil07 commentedsubscribing
Comment #2
sdboyer commentedAdding tag and un-postponing. This must happen before we can make the switch. This is probably a Novice issue for phase 2, but phase 3 will be a lot more complicated.
Comment #3
chx commentedwhile changing the cvs command strings to git clone is indeed a novice task , testing this is .... not exactly novice :D
Comment #4
sdboyer commentedSorta a meta-issue for making sure PIFR is ready for migration day.
Comment #5
boombatower commentedTwo things. PIFT runs on d.o, PIFR runs on qa.d.o and workers.
PIFR already works fine on cvs, svn, bzr, and git (respective example projects: d.o, business, examiner, just in testing). I think I need to tweak the git backend for something I found recently, but shouldn't be anything hardcoded. Only stuff that assumes CVS is on d.o since project does and it has to use what project uses, but that doesn't involve hard coded cvs strings since it just reads out of cvs module stuff. That should be related to any ports of using versioncontrol api with project nothing new.
Comment #6
boombatower commentedWell I'll leave open until I look at that git thing I mentioned, but minor.
Comment #7
sdboyer commentedOK good, I don't understand how the whole PIF... stack works. Sorry, we were just reorganizing the whole queue today :)
Comment #8
deekayen commentedJust dumping this off since I worked on it a bit. It's a git version of the integration script for project_issue_file_review/util/vcs. I haven't even tried it yet, but it follows the same format as the svn-post-commit script. Note, the git post-commit.sample file uses
#!/bin/shinstead of#!/usr/bin/php -qas this attached script does.Comment #9
boombatower commentedForgot about this issue...oh well I committed the fix.