Skip to content

Changing(rotating) plugin credentials take no effect until Jenkins is restarted due to cached repo object #856

@sp-ricard-valverde

Description

@sp-ricard-valverde

private transient GHRepository ghRepository;

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions