Travis CI #91
Travis CI #91
Conversation
| sudo: false | ||
| language: node_js | ||
| node_js: | ||
| - "0.10" |
There was a problem hiding this comment.
we might use a newer version here.
There was a problem hiding this comment.
we don't need to have multiple Node versions, we're not testing anything on Node, maybe the only issue we might have is due to dependencies, but we don't use anything else than devDeps so far.
|
LGTM. |
|
@raphamorim would you squash the commits and set a commit message based on the jQuery Commit guidelines? You may use Build as the component name. |
|
One last thing: it seems you might need to run |
raphamorim
force-pushed
the
feature/travis-ci
branch
from
228b1dc
to
9fd4630
Compare
|
I'm not sure about it, because jquery-color uses Bowercopy. Then by default, bowercopy runs |
|
the current processes here were copied from a REALLLY old version of the everything about it could use "simplifying" probably (including bowercopy, On Thu, Feb 4, 2016 at 11:38 AM, Raphael Amorim notifications@github.com
|
|
I see, I think it's better merge this PR ( 'cause probably shouldn't change the travis script) and open an issue to discuss the build improvements. |
|
I'm ok with the "progressive enhancement". I just want to turn on Travis CI before I merge this. |
|
merged at 44cbc46 👍 |
Hi @gnarf, @leobalter
I gave the kickoff for integration. I wonder if can enable jquery-color in travis.
Currently the script only runs grunt, but I'll integrate it with browserstack later.