Branch: refs/heads/master
Home: https://github.com/jenkinsci/jenkins
Commit: e76f6a293aa26eeddd6887d43a9087e38f9e103a
https://github.com/jenkinsci/jenkins/commit/e76f6a293aa26eeddd6887d43a9087e38f9e103a
Author: Jesse Glick <[email protected]>
Date: 2020-03-28 (Sat, 28 Mar 2020)
Changed paths:
M core/pom.xml
M core/src/main/java/hudson/util/HistoricalSecrets.java
M core/src/main/java/hudson/util/Secret.java
M core/src/main/java/jenkins/security/ConfidentialStore.java
M core/src/main/java/jenkins/security/DefaultConfidentialStore.java
M core/src/main/java/jenkins/security/RSAConfidentialKey.java
R core/src/test/java/hudson/util/MockSecretRule.java
M core/src/test/java/hudson/util/SecretRewriterTest.java
M core/src/test/java/hudson/util/SecretTest.java
M core/src/test/java/jenkins/security/ConfidentialStoreRule.java
M test/src/test/java/jenkins/security/RekeySecretAdminMonitorTest.java
Log Message:
-----------
Let ConfidentialKey & Secret do something from unit tests (#4603)
* Delete ConfidentialStoreRule
* Also delete MockSecretRule so Secret.fromString works
* Secret.SECRET still referenced by SecretHelper in jenkins-test-harness, used
by RekeySecretAdminMonitorTest, also copied in publish-over-*-plugin
* RSAConfidentialKey ought to use the same SecureRandom as the
ConfidentialStore; this also lets the mock use a fixed seed
* For now ConfidentialStore.secureRandom can be abstract
* Some core unit tests can be rather verbose; set
maven.test.redirectTestOutputToFile
* Looks like we need a ConfidentialStoreRule after all
* Restored another couple of usages
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/jenkins/push/refs/heads/master/f72bcc-e76f6a%40github.com.
