You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ghRepository is being cached when a successful connection is established, but if the connection credentials are ever updated during normal Jenkins operation(in our case, regular credential rotation procedures) the repo object is still reused and never invalidated until Jenkins is rebooted.
It would be nice to have a way to invalidate ghRepository when operating with it if an error is arisen from the underlying client and support updating Jenkins credentials without disrupting operation.
The text was updated successfully, but these errors were encountered:
ghprb-plugin/src/main/java/org/jenkinsci/plugins/ghprb/GhprbRepository.java
Line 63 in ebd6df7
The
ghRepository
is being cached when a successful connection is established, but if the connection credentials are ever updated during normal Jenkins operation(in our case, regular credential rotation procedures) the repo object is still reused and never invalidated until Jenkins is rebooted.It would be nice to have a way to invalidate
ghRepository
when operating with it if an error is arisen from the underlying client and support updating Jenkins credentials without disrupting operation.The text was updated successfully, but these errors were encountered: