Open philip-bradshaw opened 1 month ago
Thanks for reporting the issue. Is that a new behavior with 1.8.2 that did not happen in 1.8.1 or was the behavior the same in 1.8.1?
@MarkEWaite This was occurred on 1.8.2. We tried reverting to 1.8.1 and got the same issue. Weirdly, the issue dissapered when I was digging into the Gitlab settings in the Jenkins System settings and clicked save without changing anything. My guess is there was an issue loading the system settings or retrieving them?
If you find a way to duplicate it, please share those steps. I'm glad that the problem was not specific to 1.8.2.
Jenkins and plugins versions report
Jenkins 2.462.3 GitLab API Plugin Version 5.6.0-97.v6603a_83f8690 GitLab Plugin Version 1.8.2
What Operating System are you using (both controller, and any agents involved in the problem)?
Jenkins running as container on an Ubuntu 22.04 gen2 Vm as a part of an AKS cluster
Reproduction steps
Expected Results
Actual Results
Anything else?
We have confirmed that Jenkins is able to reach the instance of gitlab, Also that the Configuration under
Dashboard -> Manage Jenkins -> System
is valid as wellAre you interested in contributing a fix?
No response