[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. |
jglick
left a comment
There was a problem hiding this comment.
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:
ownerleft blank to infer valueThe regression was introduced since #796. The
ownerparameter is not used anymore and the credentials clone is initialized using theownerfield read method instead ofownerparameter value, resulting withnullowner 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
ownerfrom the parameter instead of clone fieldnullvalue.See JENKINS-73474 for more information.