Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Drupal to Alpaca Travis Setup #455

Closed
dannylamb opened this issue Dec 13, 2016 · 9 comments
Closed

Add Drupal to Alpaca Travis Setup #455

dannylamb opened this issue Dec 13, 2016 · 9 comments
Assignees

Comments

@dannylamb
Copy link
Contributor

We need Drupal installed in the Alpaca test environment before we can do end-to-end integration testing. Add the relevant parts of the travis setup for the islandora modules to Alpaca.

@ruebot
Copy link
Member

ruebot commented Dec 19, 2016

@dannylamb questions about the priority and need of this as I am working through Islandora/Alpaca#23:

  • What's the priority on this?
  • Is this 100%, or can we achieve the end-to-end testing another way

Asking because of the constraints of TravisCI. We are bound to an Ubuntu 12.04 machine, and that machine is either a "Java" or "PHP" machine. So, if it is a Java machine, which we are using now, we need to setup a full PHP 7 environment on it, along with MySQL and PEAR to get everything going. Or, we go the other way, and get Java environment setup on a PHP machine. So, before I go any further on this, let me know what you think.

Current status of the build with attempting a full Drupal setup can be found here: https://travis-ci.org/Islandora-CLAW/Alpaca/jobs/185176564#L171

@dannylamb
Copy link
Contributor Author

dannylamb commented Dec 19, 2016

For posterity, there was an IRC conversation about this, and we decided to move forward with putting Java onto a PHP box, since LAMP is trickier to install via travis than just Java.

And priority is fairly high, since we should be providing tests with each PR instead of slapping things together and hoping a brave soul will try to write tests for all of it after the fact.

@ruebot
Copy link
Member

ruebot commented Dec 19, 2016

@dannylamb
Copy link
Contributor Author

@ruebot Why are we bound to 12.04? I don't like the thought of being two LTS's behind if it can be avoided.

@ruebot
Copy link
Member

ruebot commented Dec 20, 2016

https://docs.travis-ci.com/user/ci-environment/ -- Honestly not sure how to force it to use 14.04, which is supposedly available.

@dannylamb
Copy link
Contributor Author

hunh, apparantly like this:

dist: trusty
sudo: required

totally out of scope for this, but good to know.

@ruebot
Copy link
Member

ruebot commented Dec 20, 2016

Hah! That totally makes sense! I'm happy to toss another commit on here if you'd like just to see if it works, and if it does, we can create a ticket to update other builds. Seems like that would be a good newbie ticket too.

@ruebot
Copy link
Member

ruebot commented Dec 20, 2016

@dannylamb added trusty in the latest code review commit.

@dannylamb
Copy link
Contributor Author

you didn't have to. but as long as there's no explosions, i don't mind ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants