Posted by boombatower on December 4, 2008 at 5:10am
2 followers
| Project: | PIFR Demo |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed (fixed) |
Issue Summary
Testers could goto testing.drupal.org press a button and have a test drupal site setup with the patch they want to test.
The instance would only be accessible to the user who created it to prevent XSS attacks. Once the user leaves or after timeout of inactivity the site would be destroyed.
I made an initial stab at this some time ago and stopped after finding: #329548: Clean up testing.drupal.org server
| Attachment | Size |
|---|---|
| pifr_environment.patch | 5.03 KB |
Comments
#1
Waiting for 2.x.
#2
Talk to sun (tha_sun) about using demo module.
#3
Workflow:
Drupal.org
* file patch
* patch is queued and has test ID assigned
* "try now" link is visible
link -> qa.drupal.org (redirect) -> dedicated demo client
demo client
* start batch process
* request test information
* perform setup routines
* auto-login
* schedule site for deletion after one hour
What is needed:
* minimal module on qa.drupal.org* perform redirect
* provide test information (simple wrapper around pifr API)
* minimal module on client
* instead of requesting tests on cron run it will provide a page to trigger
* wrap pifr client runner with batch API
* setup demo module
* auto login
possible module name: pifr_usability
#4
#5
#6
Virtually done, just need auto-login.
#7
Complete.
#8
Automatically closed -- issue fixed for 2 weeks with no activity.