One of our admins performed a YUM update on our AWS Linux Jenkins serve. CA Certs were updated as well as Jenkins. Now existing Jobs are failing and when we try to configure jobs with existing GitHub creds, we get the following errors in Jenkins:
Failed to connect to repository : Command "git ls-remote -h <SOME_GIT_REPO> HEAD" returned status code 128: stdout: stderr: fatal: unable to access '<SOME_GIT_REPO>': Peer's certificate issuer has been marked as not trusted by the user. We have verified that the cacerts used by Java were updated via YUM. Was there a change to how Jenkins uses these certs from the Java JRE? Anyone else seen this issue? -Jimmy -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5d7ef0af-e330-46f5-a004-aec17af36ed2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
