Enable travis-buddy on GitHub repos

[jayvdb]

https://github.com/bluzi/travis-buddy provides a synopsis of the travis error on the pull request

https://travisbuddy.com

[jayvdb]

I would suggest the following order

1. https://github.com/coala/documentation
2. https://github.com/coala/cEPs
3. https://github.com/coala/corobo
4. https://github.com/coala/coala-vs-code
5. https://github.com/coala/projects
6. https://github.com/coala/coala-html
7. https://github.com/coala/community
8. https://github.com/coala/coala-bears

And after each we check that it is working as expected before continuing to the next.

[manankalra]

There should be individual issues opened for this in the corresponding repos or just this issue should be referenced in the individual PRs?

[jayvdb]

No need, just use Related to https://github.com/coala/meta/issues/114

[palash25]

Can this issue have multiple assignee? I think we can complete it much faster if we divide individual repos amongst ourselves. If you don't mind @manankalra .

cc @jayvdb

[jayvdb]

Please read the issue again @palash25 .

[jayvdb]

Another option is to enable travieso

maybe we try that after travis-buddy, if we dont like travis-buddy.

c.f. coala/coala#4891

[manankalra]

travis isn't set up for cEPs; needed?

[jayvdb]

coala/documentation#555 (comment) - a buddy error. looks nice!

travis isn't set up for cEPs; needed?

ok, skip that one for now.

[manankalra]

For corobo:
As per my knowledge, travis-ci/travis-ci#5121 isn't solved yet. Also, the docs do not mention anything of this sort - https://docs.travis-ci.com/user/notifications/#Configuring-webhook-notifications.

Will have to omit on_success: never for now.

[jayvdb]

Before doing bears, here are some more to give us some experience with it

1. https://github.com/coala/coala-quickstart
2. https://github.com/coala/gci-leaders
3. https://github.com/coala/gh-board
4. https://github.com/coala/coala-emacs
5. https://github.com/coala/landing-frontend

[manankalra]

Should I open PRs for all of them?
There seems to be no ongoing contribution activities in any of the above repos (other than gh-board). Shouldn't we first test it on coala-bears then?

[bluzi]

Hey guys,

It looks like you've been using TravisBuddy for more than a month now, so I was just wondering if there's anything you think we can improve or add?

[jayvdb]

Interesting missing error at coala/corobo#550 (comment)

[manankalra]

Here, too. - coala/corobo#552

[li-boxuan]

TravisBuddy copies too much log. 😕 That's a lot of network traffic, especially when we use API to fetch comments.

[jayvdb]

Probably bluzi/travis-buddy#109 @bluzi

Also some feature requests https://github.com/bluzi/travis-buddy/issues/created_by/jayvdb

@li-boxuan , can you link to some large comments. @bluzi may know how to fix them.

[li-boxuan]

This is a large comment: coala/community#143 (comment)

[jayvdb]

Any large comments in JS projects?

TravisBuddy doesnt have code for python specific projects yet.

[bluzi]

Thanks a lot guys! that's super helpful!

---

Interesting missing error at coala/corobo#550 (comment)

Here, too. - coala/corobo#552

Thanks, will definitely look into it

---

Also some feature requests https://github.com/bluzi/travis-buddy/issues/created_by/jayvdb

Awesome, thank you!

---

This is a large comment: coala/community#143 (comment)

Definitely a bug, TravisBuddy should break the log using the scripts supplied in .travis.yml. Instead this comment contains the entire raw log.
Will look into it and get back to you.

[li-boxuan]

Not sure if this is also a 'large' comment (JS project) coala/gci-leaders#149 (comment)

[bluzi]

Not sure if this is also a 'large' comment (JS project) coala/gci-leaders#149 (comment)

Nope.
As you can see in the build log, the raw log is a lot bigger. TravisBuddy extracted the log of the executed command (npm run build), so that's by design.

[jayvdb]

@manankalra , any active repos left to enable this in?

[manankalra]

Yes. coala and coala-bears.