chef-deploy-drupal icon indicating copy to clipboard operation
chef-deploy-drupal copied to clipboard

Setup continuous integration testing

Open dergachev opened this issue 12 years ago • 3 comments

With Travis or otherwise.

This issue replaces: https://github.com/amirkdv/vagrant_drupal/issues/4 -- Setup integration testing

Resources:

  • https://github.com/amirkdv/chef-deploy-drupal/blob/master/dev-notes.md#testing
  • https://github.com/amirkdv/vagrant_drupal/issues/4

dergachev avatar Jul 02 '13 17:07 dergachev

Once #4 is done (create deploy-drupal::install recipe), then it might be possible to test on Travis without reinstalling PHP/mysql and so on. After all we're more interested in testing deploy-drupal::install than whether we can install mysql.

dergachev avatar Jul 02 '13 18:07 dergachev

FYI drush has a .travis.yml file:

http://drupalcode.org/project/drush.git/blob/refs/heads/8.x-6.x:/.travis.yml

dergachev avatar Jul 02 '13 18:07 dergachev

FYI I googled around for some alternatives to Travis-ci:

  • http://stackoverflow.com/questions/4667633/do-you-know-any-hosted-ci-server
  • https://www.openshift.com/jenkins
  • http://www.cloudbees.com/platform/pricing/devcloud.cb
    • http://www.cloudbees.com/foss/index.cb (special pricing for open source)
    • http://developer.cloudbees.com/bin/view/DEV/GitHub+Commit+Hooks+HOWTO
  • https://github.com/junit-team/junit/issues/516
  • https://github.com/openMF/mifosx/pull/234

They seem to be all hosted Jenkins, which is good if we ever want to move to self-hosted. I still suspect Travis is the easiest option at the moment.

dergachev avatar Jul 02 '13 22:07 dergachev