For proper operation of the hook scripts, we need to create some drush commands that can take arguments of the sort generated by the data that typically passes through serverside git hooks. So, the sort of data being discussed in #878278: Conceive of tests for all possible receive-pack related hooks (pre-receive, update, post-receive, and post-update).
These drush commands will probably just be thin wrappers on repo methods that fetch & parse specified commit ranges. We'll also prolly need these to be sensitive to non-ff pushes...if not now, then very VERY soon.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | versioncontrol_git-1022514-draft1.patch | 2.76 KB | jonathan webb |
Comments
Comment #1
Anonymous (not verified) commentedsubscribe.
Comment #2
Anonymous (not verified) commentedrelated ticket: #1012988: Create serverside git hooks that interact with our unique server environment.
Comment #3
sdboyer commentedPushing this back to sprint 9. Yeah, it's critical, but we've got other things to focus on at the moment which are in the way of even really being able to push.
Comment #4
jonathan webb commentedComment #5
jonathan webb commentedHere's a sketch for the drush integration side of things... This patch includes two drush commands corresponding to the server-side "pre-receive" and "update" hooks. Just checking if I'm on the right track here.
Comment #6
eliza411 commentedLeaving this open as it may become enough or may need work depending on the out come of performance testing.
Comment #7
sdboyer commentedComment #8
eliza411 commentedComment #9
sdboyer commentedwe've had these forever; this never got closed.
Comment #10
marvil07 commented