Details
-
Task
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
Description
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
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Epic Link |
|
JENKINS-38833 [ 175240 ] |
| Assignee | Oleg Nenashev [ oleg_nenashev ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Attachment | remoting-3.8-SNAPSHOT.jar [ 37485 ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
| Status | In Review [ 10005 ] | In Progress [ 3 ] |
| Remote Link | This issue links to "MJARSIGNER-53 (Web Link)" [ 17480 ] |
| Summary | Be able to release remoting without Kohsuke | Setup code signing to be able to release Remoting without Kohsuke |
| Remote Link | This issue links to "https://github.com/apache/maven-plugins/pull/125 (Web Link)" [ 17481 ] |
| Remote Link | This issue links to "https://github.com/apache/maven-shared/pull/24 (Web Link)" [ 17482 ] |
| Remote Link | This issue links to "https://github.com/jenkinsci/remoting/pull/190 (Web Link)" [ 17483 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Component/s | core [ 15593 ] |
| Remote Link | This issue links to "CloudBees Internal OSS-2227 (Web Link)" [ 18386 ] |