This would be nice for qa.drupal.org so I'm filling it here to see if it would be possible.
Currently there's no easy way to find out a project's current testing status. Sure, we added a menu link and alias straight to http://qa.drupal.org/head-status, but how do I find the current status of Poormanscron 6.x-2.x branch? I'm proposing a page that lists all the enabled 'projects' (like qa.drupal.org/pifr/projects) (and an overview if all their branches are passing) with a link to a 'project testing' summary page (like qa.drupal.org/pifr/projects/[project-id]) to show me the overview of testing status for each branch.
Doubly awesome if this information could be linked back on drupal.org as well via a link on project pages or from branch dev releases.
Comment | File | Size | Author |
---|---|---|---|
#15 | pifr_branches_view_export.txt | 9.27 KB | jthorson |
#14 | pifr-server-add_arguments_to_branchtests_view-694876-14.patch | 1.83 KB | jthorson |
#9 | rfay_dell_gazelle_Selection_024.png | 16.58 KB | rfay |
Comments
Comment #1
Dave ReidWhat would also be nice is to list the number of queued issues per-project and per-branch to see how behind/caught-up we are.
Comment #2
boombatower CreditAttribution: boombatower commentedYea, I have thought about something like this, but as of yet have not implemented it. One thing we should look into is how we want to display results of branches on d.o, but this is separate from that.
Comment #3
moshe weitzman CreditAttribution: moshe weitzman commentedI went looking for such a page today. +1.
Comment #4
jhodgdonMe too. I was just about to add a comment to the "add me to testing contrib" issue, asking how I could find the status of testing of my two modules that were added (THANKS by the way!), but found this issue...
Comment #5
jhodgdonJust as a note, on IRC boombatower pointed me to http://qa.drupal.org/pifr/log -- for now, when you submit a patch or a commit, you can go to that page and find your test results. At least until they are collected somewhere else.
Comment #6
catchThis exists now at http://qa.drupal.org/pifr/test/126149 (for entitycache).
However what I'd really like is a block on the project page. This is the closest I can find to an issue for that, so bumping this issue. If I should post it somewhere else, please say so!
Comment #7
rfayAll branch tests are available at http://qa.drupal.org/pifr/branches, so the original intent is now satisfied. Would be nice to have status on the project page though, yessirree. I wonder whose job that would be.
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous commentedThis thread was just pointed out to me on another thread (http://groups.drupal.org/node/139754#comment-527959). I'm interested in contributing to this process in some way, even though I'm not very aware of the qa.drupal.org project as a whole, I'm just going to go for it:
It looks like the first step is going to be implementing some sort of URL pattern as the OP suggests so it becomes easier to find this stuff. As a user visiting the qa.drupal.org site for the first time I can see that the site is doing a lot of amazing things, but I can't get to information that is useful to me. It took me a minute to realize there were only two pages in the pager - so not much here yet - but this obviously won't scale.
I would probably structure the URLs this way: /[project]/[branch]/[release] ... reason being if I know the URL of the project (or can easily guess), then I can quickly reference a project's status without a lot of digging around.
Getting URLs sorted would at least make it possible to find the data. I was going to suggest building a View here, but I see on the top of the branches page that there is no Views handler for something. Maybe I can help with something there? I've dealt with views handlers before... can't say it's my favourite thing to code but I'll give it a shot if this is what it takes.
If there is a listing on a per-project basis then we can start talking about exporting things to appear on drupal.org pages and elsewhere... and THAT would make my life a lot easier.
Comment #9
rfayWe might be able to do that just with arguments to the view. but...
The page with the view is http://qa.drupal.org/pifr/branches
But we don't seem to have a lot of arguments implemented:
So perhaps the first step would be to implement more views arguments. And while we're at it, sort handlers, especially for title.
Comment #10
jthorson CreditAttribution: jthorson commentedHmmm ... went to dig into this, but looks like this view isn't implemented on scratch yet. Could I ask someone with admin on qa.d.o to export the view and throw it up on the scratch site?
Comment #11
rfayI'll refresh the qa.scratch database from qa. However, to actually work on this you'll need to add new fields and sorts and filters and arguments to pifr's views implementation... Let me know when you need a dump of qa,.
Comment #12
Anonymous (not verified) CreditAttribution: Anonymous commentedI've been following some of this discussion in IRC and kudos to both @rfay and @jthorson for the awesome momentum on this. Makes me feel really good about the direction of drupal.org. If I can be of assistance please just drop a note on my contact form. I'm not setup (yet) with qa.drupal.org but I really love this idea.
Comment #13
rfay@jthorson, scratch has been refreshed from qa. You'll have to recreate your user there, sorry. Let me know and I'll promote you.
@Ryan, would love to have you aboard!
Comment #14
jthorson CreditAttribution: jthorson commentedHere's a patch to the hook_views_data() implementation, to add the required arguments (and sort capability on the 'title' field).
Comment #15
jthorson CreditAttribution: jthorson commentedAnd here's an export of the view, which should give you the sortable title and branch fields, as well as exposed filters for 'Project Title' and 'Branch', which makes it relatively trivial to filter down to the project you're looking for.
Comment #16
rfayTested it out; read the code. Looks good to me. Committed: 5123458
Thanks!
Comment #18
jthorson CreditAttribution: jthorson commentedShould we consider re-opening this and leaving it 'active' until the sort functionality is actually deployed on qa.drupal.org (and to make sure we don't lose the other enhancements that the new arguments should allow?)
Comment #19
jthorson CreditAttribution: jthorson commentedMoving to rtbc, pending actual deployment on qa.drupal.org.
Comment #20
catchOpened #1228462: Provide branch testing status and retest options on Drupal.org project pages for exposing this on d.o more.
Comment #21
jthorson CreditAttribution: jthorson commentedPreview of views sort/filter capability available at http://qa.scratch.drupal.org/pifr/branches
Comment #22
jthorson CreditAttribution: jthorson commentedTitle sort and filter capability now deployed on qa.drupal.org, at http://qa.drupal.org/pifr/branches