Setup Travis CI and Unit Tests about ng-fab-form

[lowe0292]

@johannesjo looking for any help on this? I just setup a Jenkins CI server to run unit tests on every commit and integration tests on every pull request.

[johannesjo]

@lowe0292 I would be glad for help! Thank you for the offer. I pushed the current state to the feature-branch. Its pretty messy atm, but maybe it is a good starting point.

[lowe0292]

@johannesjo sweet! What do we want to do about hosting? I typically use the smallest Digital Ocean droplet and that's $5 / month.

[johannesjo]

Actually I think the basic service Travis CI offers should be enough for the project and already works using a very simple configuration: https://travis-ci.org/johannesjo/ng-fab-form

[johannesjo]

Or do you think there are any mature advantages to a Jenkins setup that I'm missing out here?

[lowe0292]

Oh, you right! My natural inclination is Jenkins because I typically deal
with private repos and Travis is pretty expensive for private repos. I'll
get started tonight and let you know if I run into any issues.
On Dec 17, 2014 8:37 AM, "johannesjo" [email protected] wrote:

Or do you think there are any mature advantages to a Jenkins setup that
I'm missing out here?

—
Reply to this email directly or view it on GitHub
#10 (comment)
.

[johannesjo]

Shamefully expensive I would say :) but setting it up was a really easy.

Looking forward to see, what could get done. Thank you for your help!

[lowe0292]

I suppose you get what you pay for... The Jenkins setup was non-trivial,
had to install and configure a few plugins.

Do you know if I'll need write access, or will read be sufficient for
Travis?
On Dec 17, 2014 11:24 AM, "johannesjo" [email protected] wrote:

Shamefully expensive I would say :) but setting it up was a really easy.

Looking forward to see, what could get done!

—
Reply to this email directly or view it on GitHub
#10 (comment)
.

[johannesjo]

I'm new to Travis but I think read access should be sufficient. I assume that it will run for every pull-request automatically. The basic setup just uses the grunt testSingle task, which runs the unit tests for now. Just write me a message if you run into any issues.