Closed (fixed)
Project:
Project
Version:
5.x-1.x-dev
Component:
Releases
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
23 Jan 2007 at 02:58 UTC
Updated:
11 Feb 2007 at 20:02 UTC
Jump to comment: Most recent file
often when debugging problems with release nodes [1] it's handy to run the packaging script manually to see what's going on, but restrict it to a specific project. i usually just edit the script to add another WHERE clause to the query, but this is error-prone and labor-intensive. attached patch just makes it so that if you happen to specify a 2nd arg on the command-line, it treats that as the nid for the project you're interested in, and packaing (or verifying) only happens for that project.
[1] see for example:
http://drupal.org/node/111631
http://drupal.org/node/109143
or more broadly:
http://drupal.org/node/109181
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | package-release-project-arg.patch_2.txt | 5.8 KB | dww |
| #1 | package-release-project-arg.patch_1.txt | 5.29 KB | dww |
| package-release-project-arg.patch.txt | 5.29 KB | dww |
Comments
Comment #1
dwwsyntax error in previous patch.
Comment #2
dwwafter testing on s.d.o, fixed minor bug, and improved watchdog. i think this is RTBC. anyone care to take a look?
Comment #3
merlinofchaos commentedCodewise it looks good.
Question: Would this enable project administrators to maybe get a button to run the packaging script for just one project? (This might be nice for getting -dev releases built more quickly after one is put in).
Hm. As I think on it that's not a good solution.
Maybe dev releases should be built more often *if* they don't have a file; so your initial -dev release will show up right away. Hm. that's for a completely other patch and I'm just babbling here.
Comment #4
dwwthanks for the review, merlin.
yeah, for all sorts of permission/security issues, the packaging scripts run as a completely different user than the webserver, which is why it's triggered by UNIX cron, not drupal. ;) so yeah, the initial packaging for a development snapshot would require a different kind of change, not a button for project maintainers to click. for example, the 'tag' operation could be modified to also check for dev snapshots that have no file or something... but yeah, that's certainly for another issue.
committed to HEAD and installed on d.o. i'll email the infra list about this.
Comment #5
(not verified) commented