Open jayvdb opened 6 years ago
I would suggest the following order
And after each we check that it is working as expected before continuing to the next.
There should be individual issues opened for this in the corresponding repos or just this issue should be referenced in the individual PRs?
No need, just use Related to https://github.com/coala/meta/issues/114
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
Please read the issue again @palash25 .
Another option is to enable travieso
maybe we try that after travis-buddy, if we dont like travis-buddy.
travis isn't set up for cEPs; needed?
https://github.com/coala/documentation/pull/555#issuecomment-385757936 - a buddy error. looks nice!
travis isn't set up for cEPs; needed?
ok, skip that one for now.
For corobo: As per my knowledge, https://github.com/travis-ci/travis-ci/issues/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.
Before doing bears, here are some more to give us some experience with it
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?
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?
Interesting missing error at https://github.com/coala/corobo/pull/550#issuecomment-395577123
Here, too. - https://github.com/coala/corobo/pull/552
TravisBuddy copies too much log. 😕 That's a lot of network traffic, especially when we use API to fetch comments.
Probably https://github.com/bluzi/travis-buddy/issues/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.
This is a large comment: https://github.com/coala/community/pull/143#issuecomment-395946259
Any large comments in JS projects?
TravisBuddy doesnt have code for python specific projects yet.
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.
Not sure if this is also a 'large' comment (JS project) https://github.com/coala/gci-leaders/pull/149#issuecomment-386820394
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.
@manankalra , any active repos left to enable this in?
Yes. coala and coala-bears.
https://github.com/bluzi/travis-buddy provides a synopsis of the travis error on the pull request
https://travisbuddy.com