Travis builds for plugins

[var-foo]

I'm going to make a travis CI build for plugins. Here's what I'm thinking:

• execute unit tests (first iteration)
• check for proper file structure (probably later iteration)
• phpdoc - to publish... to the github page?

Does this need to do anything else?

[scottux]

phpdoc - to publish... to the github page?

Yes. If we can commit back to qcubed/github.qcubed.com and ensure the documentation is generated using a proper theme, I think that would be the best solution.

we can lint the js/css and ensure proper code standards. We will definitely need to iterate over it.

[var-foo]

I haven't gotten that far, but it appears so since I have full access to a debian vm from what I can tell.

I agree, iterations.