I think we should experiment with using Apache or nginx rather than the PHP webserver and see if/how it works.

The pro's are:

  • It might run faster! This would make working with Travis-CI more pleasant.
  • It would allow us to test PHP 5.3. The PHP webserver is only in 5.4 or higher. Since Panopoly runs on 5.3, we should probably test it.
  • It will better resemble a really site. There maybe situations where the PHP webserver will act differently than a real webserver.

The con's are:

  • It might run slower.. It already takes about 20 minutes to run a single build. If it got slower, that would not be optimal.
  • Increased complexity. Configuring Apache or nginx will make the Travis-CI script more complex.
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dsnopek’s picture

Component: Code » Admin

Here's some Travis-CI docs on configuring Apache:

http://docs.travis-ci.com/user/languages/php/#Apache-%2B-PHP

dsnopek’s picture

Component: Admin » Tests / Continuous Integration
dsnopek’s picture

dsnopek’s picture

Status: Active » Needs work
FileSize
2.61 KB

Here's the first attempt at a patch, but fails:

https://travis-ci.org/dsnopek/panopoly/builds/52334710

mglaman’s picture

Status: Needs work » Closed (won't fix)

I found this via a Google search on something. Panopoly is using drupal_ti now, figure I could go ahead and mark this as a won't fix to tidy up the queue.

dsnopek’s picture

Status: Closed (won't fix) » Needs work

@mglaman: Thanks for doing issue triage! However, I think I'd prefer to keep this one open, even if we toss out the existing patch. With drupal_ti, we're still using the PHP webserver, and there still may be reasons to convert to using Apache or nginx.

heddn’s picture

For those following, https://github.com/MTechLLC/nica/blob/master/.travis.yml is a working setup using php 7, apache and fastcgi. I think you just have to delete one line in the "enable php-fpm" section.