Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2043

Mirror Jenkins plugins - Auto

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

       
      Hi Team,
       
      We want to use our on-premise update center instead of the default update center for jenkins, for that we have created a mirror to Jenkins plugin repo on our Artifactory and used the https://github.com/ikedam/backend-update-center2 to create our own update-center.json with required plugins that we use.
      Upon updating the default update site url with our internal Artifactory update-center.json url we are getting the signature not verified error.I have added the internal ca certificate to the java cacerts as well but still getting the same error.
       
      Is there a way we can use the internal update center for the Jenkins plugins instead of the default one?
       
      I have attached the error details to this ticket.
       
      Thanks
      Kushal

        Attachments

          Activity

          kushalrreddy kushal Reddy created issue -
          kushalrreddy kushal Reddy made changes -
          Field Original Value New Value
          Description As an ACoP engineer, I want to have all Jenkins plugins mirrored inside the SIC perimeter
          so that, they can be used at any time to support Jenkins builds.

           
          Hi Team,
           
          We want to use our on-premise update center instead of the default update center for jenkins, for that we have created a mirror to Jenkins plugin repo on our Artifactory and used the [https://github.com/ikedam/backend-update-center2] to create our own update-center.json with required plugins that we use.
          Upon updating the default update site url with our internal Artifactory update-center.json url we are getting the signature not verified error.I have added the internal ca certificate to the java cacerts as well but still getting the same error.
           
          Is there a way we can use the internal update center for the Jenkins plugins instead of the default one?
           
          I have attached the error details to this ticket.
           
          Thanks
          Kushal
           
           Hi Team,
            
           We want to use our on-premise update center instead of the default update center for jenkins, for that we have created a mirror to Jenkins plugin repo on our Artifactory and used the [https://github.com/ikedam/backend-update-center2] to create our own update-center.json with required plugins that we use.
           Upon updating the default update site url with our internal Artifactory update-center.json url we are getting the signature not verified error.I have added the internal ca certificate to the java cacerts as well but still getting the same error.
            
           Is there a way we can use the internal update center for the Jenkins plugins instead of the default one?
            
           I have attached the error details to this ticket.
            
           Thanks
           Kushal
          kushalrreddy kushal Reddy made changes -
          Priority Blocker [ 1 ] Major [ 3 ]
          kushalrreddy kushal Reddy made changes -
          Priority Major [ 3 ] Blocker [ 1 ]
          kushalrreddy kushal Reddy made changes -
          Assignee jenkins admin [ administrators ]
          kushalrreddy kushal Reddy made changes -
          Assignee jenkins admin [ administrators ] andrew sff [ andrew ]
          kushalrreddy kushal Reddy made changes -
          Assignee andrew sff [ andrew ] Andrew Bayer [ abayer ]
          rtyler R. Tyler Croy made changes -
          Resolution Won't Do [ 10001 ]
          Status Open [ 1 ] Closed [ 6 ]

            People

            Assignee:
            abayer Andrew Bayer
            Reporter:
            kushalrreddy kushal Reddy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: