Open mikaelarguedas opened 6 years ago
This requires GitHub API Plugin 1.90 (we are currently using 1.86). See https://issues.jenkins-ci.org/browse/JENKINS-47601
There's an issue posted with 1.89 and 1.90 https://issues.jenkins-ci.org/browse/JENKINS-47848
The reporter gets a null pointer exception on each PR. Should keep an eye on that before upgrading to fix these as the build does not fail and the commit status is able to post.
Edit: Subscribed to that issue so I can keep an eye on it.
Should we try to upgrade to check that the referenced issue actually affects us?
Waiting on a release with this PR merged https://github.com/kohsuke/github-api/pull/396
If we're waiting too long and I can drain the queue of other pressing matters we could build the plugin bundle ourselves.
If we're waiting too long and I can drain the queue of other pressing matters we could build the plugin bundle ourselves.
kohsuke/github-api#395 already references a custom build version of the plugin. But before going that route I think it makes the most sense to actually comment on the pending PR to raise awareness and get the maintainer to merge and release it upstream. Therefore I just commented on the upstream ticket.
The fix has been released in GitHub API version 1.92.
That version has never been released and then the repository was moved. The problem is tracked in jenkinsci/github-api-plugin#19.
github-api
version 1.95 is available as of today.
Both the GitHub API and GitHub pull request builder plugins are being updated to their latest version in #207. The pull request builder plugin is now recommending that people migrate to the GitHub Branch Source but I haven't yet evaluated whether it will meet our needs.
Looks to be because the id is bigger than the allowed range for an int. Example job: http://build.ros.org/job/Ipr__nodelet_core__ubuntu_trusty_amd64/47/console
Reduced error log snippet,
@nuclearsandwich FYI