-
Improvement
-
Resolution: Fixed
-
Minor
Follow-up to JENKINS-31562.
It would be great to have a test which verifies Remoting certificates on the master side. It would prevent the Core from pulling in an updated package OR from releasing with improperly signed artifact.
- relates to
-
JENKINS-31562 Remoting release process should fail if the certificate is outdated.
-
- Resolved
-
[JENKINS-49905] Jenkins core build should verify Remoting code signing during the release
Link |
New:
This issue relates to |
Assignee | New: Leonardo Rossetti [ lrossett ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Link | New: This issue is related to INFRA-910 [ INFRA-910 ] |
It is newbie friendly, because the code signing code is already available in Remoting's pom.xml. Somebody needs to reapply it to the core