Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37567

Setup code signing to be able to release Remoting without Kohsuke

    XMLWordPrintable

Details

    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

        Activity

          oleg_nenashev Oleg Nenashev added a comment -

          I finally figured out why the signing does not work as expected on my machine. I need to add a new "certchain" option to Maven JarSigner. It is tracked as https://issues.apache.org/jira/browse/MJARSIGNER-53  . I am going to workaround it and use a custom build for a while using Maven profiles.

          oleg_nenashev Oleg Nenashev added a comment - I finally figured out why the signing does not work as expected on my machine. I need to add a new "certchain" option to Maven JarSigner. It is tracked as https://issues.apache.org/jira/browse/MJARSIGNER-53   . I am going to workaround it and use a custom build for a while using Maven profiles.

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          pom.xml
          http://jenkins-ci.org/commit/remoting/99ffa3c0519743319767b372df452eb7e02c5b66
          Log:
          JENKINS-37567 - Add option to specify certchain, enforce certificate checks

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/remoting/99ffa3c0519743319767b372df452eb7e02c5b66 Log: JENKINS-37567 - Add option to specify certchain, enforce certificate checks

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          pom.xml
          http://jenkins-ci.org/commit/remoting/ca48837eec5f9cea18653528ac68ce041cdc656c
          Log:
          Merge pull request #190 from oleg-nenashev/buildflow/JENKINS-37567

          JENKINS-37567 - Add option to specify certchain, enforce certificate checks

          Compare: https://github.com/jenkinsci/remoting/compare/a052a5ac45b3...ca48837eec5f

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/remoting/ca48837eec5f9cea18653528ac68ce041cdc656c Log: Merge pull request #190 from oleg-nenashev/buildflow/ JENKINS-37567 JENKINS-37567 - Add option to specify certchain, enforce certificate checks Compare: https://github.com/jenkinsci/remoting/compare/a052a5ac45b3...ca48837eec5f
          oleg_nenashev Oleg Nenashev added a comment - - edited

          The fix has been integrated towards Remoting 3.11 and Jenkins 2.76

          oleg_nenashev Oleg Nenashev added a comment - - edited The fix has been integrated towards Remoting 3.11 and Jenkins 2.76

          Code changed in jenkins
          User: Oleg Nenashev
          Path:
          pom.xml
          http://jenkins-ci.org/commit/remoting/bc9be8a75f0a3a36e1a0f57fa3130645ed319121
          Log:
          JENKINS-37567 - Add option to specify certchain, enforce certificate checks

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/remoting/bc9be8a75f0a3a36e1a0f57fa3130645ed319121 Log: JENKINS-37567 - Add option to specify certchain, enforce certificate checks

          People

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: