Article Overview:
This article will cover how you can achieve the following:
Address and resolve the CRYPT_E_NO_REVOCATION_CHECK
error encountered during Jenkins setup.
Problem Statement:
While setting up Jenkins, you may encounter the following error:CRYPT_E_NO_REVOCATION_CHECK (0x80092012)
This indicates that the revocation function was unable to check the revocation status for the certificate.
Solution:
-
Identify the Cause:
- This error can occur due to restrictions imposed by the system's antivirus software, which may interfere with the certificate revocation check during the Jenkins pipeline execution.
- This error can occur due to restrictions imposed by the system's antivirus software, which may interfere with the certificate revocation check during the Jenkins pipeline execution.
-
Resolution Steps:
-
Pause or Stop the Antivirus Process: Temporarily pause or stop the system's antivirus process during the Jenkins setup or pipeline execution where this error occurs on your local machine.
-
Test the Pipeline: After pausing or stopping the antivirus, rerun the Jenkins pipeline to verify if the issue is resolved.
Reference:
This solution was identified and successfully implemented based on an external resource (link) that provided insights into managing certificate revocation issues. -
Pause or Stop the Antivirus Process: Temporarily pause or stop the system's antivirus process during the Jenkins setup or pipeline execution where this error occurs on your local machine.
Examples:
-
Scenario: During Jenkins setup, the pipeline fails due to the
CRYPT_E_NO_REVOCATION_CHECK
error. - Solution: Pausing or stopping the antivirus process allowed the pipeline to execute successfully, resolving the certificate revocation check issue.
Comments
0 comments
Please sign in to leave a comment.