-
Task
-
Resolution: Fixed
-
Critical
-
None
Currently remoting can be released by kohsuke only, and it complicates the things especially since we want to establish a remoting backporting flow for remoting 2.
I should get a verified key and start releasing remoting without it.
Getting of the organization key is complicated according to our last investigation
[JENKINS-37567] Setup code signing to be able to release Remoting without Kohsuke
Epic Link |
New:
|
Epic Link |
Original:
|
New: JENKINS-38833 [ 175240 ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Attachment | New: remoting-3.8-SNAPSHOT.jar [ 37485 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Status | Original: In Review [ 10005 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "MJARSIGNER-53 (Web Link)" [ 17480 ] |
Summary | Original: Be able to release remoting without Kohsuke | New: Setup code signing to be able to release Remoting without Kohsuke |
Remote Link | New: This issue links to "https://github.com/apache/maven-plugins/pull/125 (Web Link)" [ 17481 ] |