Plots2: Travis build failing

Created on 12 Aug 2019  Â·  14Comments  Â·  Source: publiclab/plots2

Travis build is currently exiting with this failure for all the recent pull requests...
With this error
/usr/local/bundle/gems/octokit-4.14.0/lib/octokit/response/raise_error.rb:16:in `on_complete': GET https://api.github.com/repos/publiclab/plots2/pulls/6124: 401 - Bad credentials // See: https://developer.github.com/v3 (Octokit::Unauthorized)

travis

@publiclab/reviewers any ideas on how to solve this? Thanks

high-priority

Most helpful comment

Looks like this worked for plots2!!!

All 14 comments

@cesswairimu I googled the error message and got to this page, someone from PL actually posted this question there. https://github.com/travis-ci/travis-ci/issues/8018
So I would try this suggestion:

"@namangupta01 I got this recently for a repo on travis-ci.com after the move to GitHub Apps.
Solved it by adding the --pro flag to travis setup releases."

Great, thanks @sashadev-sky

We faced this issue nearly a year ago too - https://github.com/publiclab/plots2/issues/2758 and it was solved by generating new token for Travis CI

Thanks @gauravano, are you have access to generate another token?

No, I don't. @jywarren or @icarito can do that

Oh I'm facing the same issue here while trying to set up dangerbot https://github.com/publiclab/mapknitter/pull/926

I think it's an issue with the dangerbot token?
We can try commenting out the danger command temporarily till this is fixed so we can see the builds

Ah, ok, so do we need to generate a new token, or has TravisCI moved to
GitHub apps and there is some other way? Thanks, all!

On Mon, Aug 12, 2019 at 4:18 AM Kaustubh Nair notifications@github.com
wrote:

I think it's an issue with the dangerbot token?
We can try commenting out the danger command temporarily till this is
fixed so we can see the builds

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/6128?email_source=notifications&email_token=AAAF6J75UVWQPR427BDNHNTQEEMCNA5CNFSM4IK44P52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4B3ACY#issuecomment-520335371,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAF6J4L2K5KTYQ7TPG2QT3QEEMCNANCNFSM4IK44P5Q
.

I think @gauravano said in the call that we need a new token!

On Wed, Aug 14, 2019, 8:43 PM Jeffrey Warren notifications@github.com
wrote:

Ah, ok, so do we need to generate a new token, or has TravisCI moved to
GitHub apps and there is some other way? Thanks, all!

On Mon, Aug 12, 2019 at 4:18 AM Kaustubh Nair notifications@github.com
wrote:

I think it's an issue with the dangerbot token?
We can try commenting out the danger command temporarily till this is
fixed so we can see the builds

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/publiclab/plots2/issues/6128?email_source=notifications&email_token=AAAF6J75UVWQPR427BDNHNTQEEMCNA5CNFSM4IK44P52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4B3ACY#issuecomment-520335371
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAAF6J4L2K5KTYQ7TPG2QT3QEEMCNANCNFSM4IK44P5Q

.

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/6128?email_source=notifications&email_token=AJXHQZ2STL4LRSSJ5YSM45LQEQOJJA5CNFSM4IK44P52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4JD4LY#issuecomment-521289263,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJXHQZ4MGACD7WWJMDYWAMLQEQOJJANCNFSM4IK44P5Q
.

OK, working on this now!

OK, just as in https://github.com/publiclab/plots2/issues/2758#issuecomment-409355915, I added a DANGER_GITHUB_API_TOKEN set to display value in build log-- following instructions at https://danger.systems/guides/getting_started.html#setting-up-an-access-token, and generated the token at https://github.com/settings/tokens

@kaustubh-nair i also repeated this for MapKnitter; can you try restarting some tests to see if it works? Thanks!

Looks like this worked for plots2!!!

Thank you @jywarren!!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

keshavsethi picture keshavsethi  Â·  3Comments

jywarren picture jywarren  Â·  3Comments

keshavsethi picture keshavsethi  Â·  3Comments

shapironick picture shapironick  Â·  3Comments

bronwen9 picture bronwen9  Â·  3Comments