A Drush task for Phing. This task enable usage of Drush commands in Phing build scripts.
Phing provides tools for usual tasks for PHP projects (phplint, jslint, VCS checkouts, files copy or merge, packaging, upload, etc.). Integration of Drush in Phing is particularly useful when building and testing Drupal projects in a continuous integration server such as Jenkins.
Project link: http://drupal.org/sandbox/mongolito404/1157574
Git repo: git clone --branch master http://git.drupal.org/sandbox/mongolito404/1157574.git phing_drush_task
The project is not linked to any specific version of Drupal
Comments
Comment #1
klausiWhat are the differences to drush_make? http://drupal.org/project/drush_make
Is it worth to have two different build solutions for Drupal? Have you talked to the drush_make maintainers or filed an issue there? What does your project accomplish that cannot be done with drush_make?
Comment #2
pbuyle commentedPhing provides tools for usual tasks when building PHP projects (phplint, jslint, VCS checkouts, files copy or merge, packaging, upload, etc.). Drush make only handle pulling resources. Both tools are complementary. Phing allows the execution of various drush commands such as make, site-install, test-run, coder review, etc. through an XML file. The Phing Drush Task eases the execution of these commands and simplifies writing the XML file. See the project description for links to more information about Phing and a sample build file.
Comment #3
klausi* Add that difference to drush_make to the project page. Others might be wondering as well.
* README.txt is missing
* "// Collect Drush output for display through Phing's log" comments should end with a "."
* installation instructions are missing, where do I have to put that file?
Comment #4
pbuyle commentedI'm feeling I'm pushed out here, that my work is not welcome.
* The difference between Drush (make) and Phing is obvious to anybody knowing what Phing and Drush are. Being an integration of Drush for Phing, the project is useless to anybody not knowing them.
* Installation instructions are redundant with Phing's own manual which already cover using additional tasks.
* Usage instructions are kindly provided in the referenced template build file.
I'll do my best to comply, but I really have the feeling that I have to waste my time in order to comply with general rules that don't fully apply here. Quite a few people are already using the project and, as attested by the issue queue, no one had issue with differencing it from Drush or using it. Although not mentioned during the talk, the project was used in the Continuous Integration presentation at the London DrupalCon.
Comment #5
klausiThere are users that will come to your project page with no idea whatever phing is. There will be users that will stumble upon your repository and will wonder what the heck it is. Just want to ensure that a minimum of documentation is present. So you could simply point to the phing manual in your README.txt.
The code itself looks good, I think this is nearly ready.
Comment #6
pbuyle commented* README.txt added
* Dots added in comments
* Basic usage instruction provided
I'm open to any suggestions to make the difference between Phing, the Phing Drush Task and Drusk Make more clear. It may me short, but the current description says it all. IMHO, the link to Phing and the well-knowness of Drush should be enough. Drush itself is not a general build tools, nor is Drush Make. None of them makes that claims in their description or documentation.
Comment #7
klausiThank you. RTBC for me now.
Another minor thing: lines in README.txt should not exceed 80 characters :-P
Comment #8
rfayGit vetted user role granted! Thanks for your contributions and future contributions! Thanks to the reviewers, and thanks all for your patience with this process (we hope to make it easier soon).
Comment #10
avpaderno