Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins job is green but in pull request it displayes in the "Pending status" #14108

Closed
Ohrimenko1988 opened this issue Aug 2, 2019 · 7 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.
Milestone

Comments

@Ohrimenko1988
Copy link
Contributor

Describe the bug

Jenkins job is green but in pull request, it displayes in the "Pending status"

Screenshot from 2019-08-02 17-42-30

Screenshot from 2019-08-02 17-43-19

@Ohrimenko1988 Ohrimenko1988 added kind/bug Outline of a bug - must adhere to the bug report template. team/che-qe labels Aug 2, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 2, 2019
@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Aug 2, 2019

That is known problem. The problem is that API rate limit exceeded for the personal GitHub account which we uses for the job which checks PR.
Possible solution is to use "che-bot" account instead of personal account to communicate with GitHub.

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Aug 2, 2019

This issue is kind of blocker for #14068.

@benoitf benoitf added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 5, 2019
@benoitf benoitf added this to the 7.0.0 milestone Aug 5, 2019
@benoitf
Copy link
Contributor

benoitf commented Aug 5, 2019

@dmytro-ndp BTW I don't see why che-bot would help. it's still a github issue and the same limit will apply. che-bot should only be used when write access is used, for read operations you should use other tokens to lower the rate API limit.

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Aug 5, 2019

It requires write access as well - to set PR check status and to leave comment. That was a reason to request che-bot for Codenvy CI https://bugs.eclipse.org/bugs/show_bug.cgi?id=536913 , and here, on CRW CI, we are having the same task.

@dmytro-ndp
Copy link
Contributor

Jenkins job has been switched to use che-bot.

@Ohrimenko1988
Copy link
Contributor Author

Ohrimenko1988 commented Aug 6, 2019

@dmytro-ndp could you close this issue if bug not reproduce?

@dmytro-ndp
Copy link
Contributor

PR check Jenkins job hasn't run into that problem during the day after switching to che-bot account, so I am closing the issue as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants