On Sun, Jan 19, 2014 at 12:58 PM, Matt Ficken <themattfic...@gmail.com> wrote: > What about posting my test results on qa.php.net? The summary email > messages could continue as is, or only include a link to the appropriate > part of qa.php.net or I could stop sending them too.
Since the tool is developed by external entity and hosted outside of php.net and not developed as a PHP project I don't think its appropriate to list the results of it on qa.php.net. If however the project is moved into the php.net domain then I think that would be a fantastic idea! > I have created a mock-up of what that patch to qa.php.net might look like. > > You can see it here: > http://131.107.220.66/PFTT-Results/qa.php.net/qa-reports.htm Looks good :) > Implementation wise, I can FTP(S)/SFTP the reports as flat files up to > qa.php.net where PHP scripts would just get a directory listing to generate > the list of branches, builds, revisions and reports. This avoids creating > some complex web service or RDBMS system (which couldn't really hold all > the test data anyway). It sounds like the intentions are to allow the script to be executed on multiple environments, and maybe extended to run other apps too, so it wouldn't just be "your environment" that would need to upload the data file. I don't think we want to add another service, such as ftp(s)/sftp to that box, but rather a trivial upload endpoint so uploading the data files could be automated in a sane way. If these are expected to be executed on "build servers" then we just need our traditional token exported on those servers... -Hannes -- PHP Quality Assurance Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
