-
Notifications
You must be signed in to change notification settings - Fork 370
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-73474] Fix GitHubAppCredentials owner inference #803
Conversation
@jeromepochat What do you think about trying to create a WireMock-based regression test for this logic? It seems undesirable that something like this was not caught by tests. |
I agreed with @dwnusbaum. Please expedite this process because the latest version of the plugin is tied to the latest version of Jenkins. Many of our pipelines are currently blocked right now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks right. As a regression, I would recommend releasing immediately and spend time on a proper integration test for the whole system as a follow-up.
Agree. I'll create another PR for the integration test ASAP. BTW, can anyone merge this one please as I don't have the permission? Thanks! |
|
GitHub App installed in multiple organizations get:
Steps to reproduce:
owner
left blank to infer valueThe regression was introduced since #796. The
owner
parameter is not used anymore and the credentials clone is initialized using theowner
field read method instead ofowner
parameter value, resulting withnull
owner in the cloned credentials. While generating the token, there is no installation matching with empty owner, resulting in exception.This fix the credentials clone by setting the
owner
from the parameter instead of clone fieldnull
value.See JENKINS-73474 for more information.