You can clone with
HTTPS or Subversion.
All specs fixed on JRuby. [ci skip]
Allow JRuby to fail.
I'm running out of time, will come back later
to fix JRuby specs.
Move gems into :development group.
This avoids unnecessary gem installation
on Travis CI.
Try JRuby build.
Enable C Ext for JRuby.
Notify only Guard core members from Travis.
Add allowed to fail config for Travis.
Comment back jruby on travis
Add @Maher4Ever's email to travis-notifications and enable travis-bui…
…lds for the listen branch
Revert "Try JRuby on Travis CI."
This reverts commit 420d3ef.
Try JRuby on Travis CI.
Revert "Try JRuby on Travis."
This reverts commit 83fe392.
Try JRuby on Travis.
Pause JRuby builds on Travis.
It seems that Travis currently has some problems with running the Guard
specs on JRuby. Needs some further investigations on what to problem is.
Bundle dev gems on Travis.
Add rbx and jruby 1.8 and 1.9 modes.
Remove dev branch from Travis config.
Remove Rubinius 1.2.4 from Travis.
Test also on stable Rubinius 1.2.4
Test Guard on Ruby 1.9.3.
Remove notifications branch from Travis.
Add new development branch to Travis.
Add notifications branch to Travis. [ci skip]
Decrease Travis sleep time.
Make spec sleep time a float.
Set a generous spec sleep time on Travis.
Build only master and guard_dependencies branches on Travis
Remove jruby_spec branch from Travis.
Merge branch 'master' of github.com:guard/guard
Configure Travis to build new branches.
Tell Travis-CI to notify only the core team.
Currently it notifies some people but I don't get how they are chosen, it even notifies me on 2 email addresses (my current and my former registered on GitHub)…
Working on a fork with Travis won't work. Re-add feature branch.
Remove testing branch.
Add JRuby/Travis test branch to CI.