Continuous Integration about wet-boew

[LaurentGoderre]

Unfortunately we are not using any right now. I am actually quite annoyed that we're committing the result of the build in the repo. In reality what happens is that someone commits change, forgets to build or have an outdated build so a separate commit has to be made just for the build. A CI that would build and deal with this outside the repository would be ideal.

[sylus]

Yeah Laurent I completely agree with you. This is definitely something we need to fix ASAP.

Ideally I think time should be devoted to set up a Jenkins server for this. We could likely setup a micro or small instance on Amazon EC2 for this very purpose. Amazon offers the Micro Instance free for year http://aws.amazon.com/free/ and I believe for subsequent years the bill only is about $50-$70. The only downside is maintenance and the odd security patch.

Unless there are some more novel ideas? IRCAN?

[sylus]

Another option might be: http://travis-ci.org/

Have never tried it but certainly looks interesting and works with github spendidly. Travis can handle build from a variety of backends such as ant, java, javascript, ruby and php

All you really have to do is add a github service hook and add a .travis.yml file in your root directory with the appropriate specifications.

Did I also mention it is open source and free!

[sylus]

Actually travis-ci.org is kind of amazing. Would love it if someone else could take a look and evaluate it as well but I can't say enough how amazing the platform is. :)

I did run into a problem of making Travis detect github organizations but was easily fixed by manually created the service hook.

Travis itself can detect when you do a push to github and that will trigger a build on the Travis CI server.

Travis does its operations your repo by reading a .travis.yml which will tell Travis what type of build to perform and additionally what kind of dependencies are needed before tests are run. (You can even use apt-get for dependencies!)

For my specific Drupal set-up all I had to do was the following (though still tinkering):

1. Manually created the .travis.yml file in my repository and paste the following content

language: php

php:

• 5.3
• 5.4

mysql:
database: wetkit_db
username: root
encoding: utf8

before_script:

• mysql -e 'create database wetkit_db;'
• pyrus channel-discover pear.drush.org
• pyrus install drush/drush
• phpenv rehash
• drush make distro.build ../github_wet_distro
• cd ../github_wet_distro
• drush si webexp webexp_theme_form.theme=web_usability_zen --sites-subdir=default --db-url=mysql://root:@localhost/wetkit_db --account-name=admin --account-pass=St@tcan@2012 --site-mail=[email protected] --site-name="Web Experience Toolkit" --yes
• cd sites/default

script:

• drush test-run

2. Go to my specific Travis page which was automatically created even with past builds at: http://travis-ci.org/#!/Web-Experience-Toolkit/Drupal7-WET-Distro

3. Click on the specific Job I would like to see the build out process for.

4. You can even include the current status of the travis build in the readme.md markdown for your repo!

[sylus]

@pjackson28 @LaurentGoderre Opinions? :)

[LaurentGoderre]

Due to the volume of work to be done, I don't think @pjackson28 and I will have the time to look into this for a while but it would be nice if someone had the time to setup a prototype.

[nschonni]

You could also try the free TeamCity (for OSS project) instance hosted by CodeBetter http://codebetter.com/codebetter-ci/

[sylus]

Basic integration has been added as per issue #23. We can look into this more closely down the line but wanted to get something basic working and we did! Just click on the build status image in readme.md to see the ant build.