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
I think we don't need to record the fingerprints when we archive. If so, I would propose to turn it off. Otherwise, we will need to add the switch to turn it on and off based on whether the OS is in FIPS mode (as a workaround for now).
If the OS is in FIPS mode, MD5 is not available and we will get the following error in the test build
internal issue
Jenkins can record the 'fingerprint' of files (most often jar files) to keep track of where/when those files are produced and used.
https://www.jenkins.io/doc/pipeline/steps/core/I think we don't need to record the fingerprints when we archive. If so, I would propose to turn it off. Otherwise, we will need to add the switch to turn it on and off based on whether the OS is in FIPS mode (as a workaround for now).
@smlambert what do you think?
The text was updated successfully, but these errors were encountered: