Added log streaming support

[Aaron1011]

This resolves issue #15

[rkh]

Oh my god. <3

Can you look into the 1.8 failures?

[rkh]

Also, we should integrate that with the travis logs command.

[Aaron1011]

Oh wow! I completely missed those failures! I'll look into that right away.

[Aaron1011]

Oh, whoops, I found the problem. I didn't read the pusher-client docs 😄 . I'll fix it.

[Aaron1011]

Ugh, there is a problem with Rubinius. I'm looking into it...

[Aaron1011]

Hmm, I haven't been able to reproduce the error locally. Do you have any ideas, @rkh?

[rkh]

@Aaron1011 I don't know. Can you maybe ping someone in #rubinius on freenode about this? Heading out, can also spin up a debug VM later.

One thing you can also try is running Rubinius in 1.9 mode (simply edit the .travis.yml).

[Aaron1011]

I realized that the reason for the failure on Ruby 1.8 with openssl-nonblock was because pusher-client tried to require it, preventing a module from loading. I've modified the Gemfile to point to my fork of pusher-client which removes all uses of openssl-nonblock.

[rkh]

Sorry, pusher-client needs to go to the gemspec, could you open an issue with them about this?

[simi]

@rkh pusher-community/pusher-websocket-ruby#16

[rkh]

\o/

[Aaron1011]

I'm starting to think that pusher-ruby-client might be unmaintained (the last activity was three months ago). I think it might be a good idea to publish a fork of it it RubyGems, and use that instead.

[joshk]

It shouldn't be unmaintained, it is looked after by pusher. We can reach out to them?

[Aaron1011]

According to this, they don't provide "official support" for the Ruby client. But I do agree that we should reach out to them.

[Aaron1011]

I've contacted Pusher through their support form. Hopefully, they will take a look at my PR soon.

[adamyeats-zz]

I've merged this for you now, guys. Sorry about the delay!

[Aaron1011]

I'll add it to the gemspec.

[Aaron1011]

@adamyeats is deploying pusher-client to RubyGems, then this can be merged.

[adamyeats-zz]

This should be deployed now, @Aaron1011. Thanks!

[Aaron1011]

@rkh: I'm going to squash the commits into one. Everything should be good to merge.

[rkh]

This is a really good start, but exposes the fact that we use pusher a bit too much. I think I'll merge it into a branch so I can work on it, too.

[Aaron1011]

Okay, sounds good! Sorry about the problems.

[rkh]

No need to apologise. I need to figure out how to get this working with pro.

[Aaron1011]

I've allowed the api key to be passed as a parameter, but I'm not sure of the best way to have it use the Pro api key.

[sarahhodne]

The API key is available through the API:

› curl https://api.travis-ci.org/config
{
  "config": {
    "host": "travis-ci.org",
    "shorten_host": "trvs.io",
    "assets": {
      "host": "travis-ci.org",
      "version": "asset-id",
      "interval": 15
    },
    "pusher": {
      "key": "5df8ac576dcccf4fd076"
    }
  }
}

Of course, the Pro API requires more things such as authenticating against the Pusher stream, which I don't really know how works.

[Aaron1011]

@rkh: Thanks for all of the additional code you added to this! It looks awesome! Sorry about the small amount I ended up contributing.

[rkh]

Don't worry, your code made me understand how the pusher client works.