InfrastructureIcon indicating the project type

Infrastructure

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

Releasing plugins is not possible as Artifactory is refusing credentials

    Details

    • Similar Issues:

      Description

      Several people have reported getting 401 errors from maven.jenkins-ci.org when attempting to release plugins.

      This has been the case for a few days, the Twitter bot shows no new plugin releases since February 9th: https://twitter.com/jenkins_release

      Some mailing list references:
      https://groups.google.com/forum/#!topic/jenkinsci-dev/ftfibR23v5Y

      I can log in to https://jenkins-ci.org/account, but https://repo.jenkins-ci.org refused my login, I guess that's why I received a 401 during mvn deploy.

      Is there anything changed on Artifactory access?

      https://groups.google.com/forum/#!topic/jenkinsci-dev/x36Si5Gc8sI
      https://groups.google.com/forum/#!topic/jenkinsci-dev/shPgezYr_xk

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          sag47 Sam Gleske added a comment -

          There still have been no releases of any plugins since Feb 8th. I just tested and I'm still not able to release the slack plugin.

          Show
          sag47 Sam Gleske added a comment - There still have been no releases of any plugins since Feb 8th. I just tested and I'm still not able to release the slack plugin.
          Hide
          Permalink
          madsnielsen Mads Nielsen added a comment -

          I tried logging into artifactory with my crendentials. I'm seeing the same issue.

          Show
          madsnielsen Mads Nielsen added a comment - I tried logging into artifactory with my crendentials. I'm seeing the same issue.
          Hide
          Permalink
          kohsuke Kohsuke Kawaguchi added a comment -

          The problem was on our side. SSL certificate has expired, and the new one was installed, but ldapd was not restarted and therefore it didn't pick up the new certificate. Once I figured out what was going on, all I had to do was to restart ldapd.

          This happened the last time I updated SSL certificate, too. I'm going to add automatic daily restart of slapd, so that the manual intervention like this won't be necessary.

          To make the matters worse, this happened while I was traveling for a whole week. My apologies for a delay in resolving this issue.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - The problem was on our side. SSL certificate has expired, and the new one was installed, but ldapd was not restarted and therefore it didn't pick up the new certificate. Once I figured out what was going on, all I had to do was to restart ldapd. This happened the last time I updated SSL certificate, too. I'm going to add automatic daily restart of slapd, so that the manual intervention like this won't be necessary. To make the matters worse, this happened while I was traveling for a whole week. My apologies for a delay in resolving this issue.
          Hide
          Permalink
          integer Kanstantsin Shautsou added a comment -

          @kohsuke, can somebody backup you in future for such cases?

          Show
          integer Kanstantsin Shautsou added a comment - @kohsuke, can somebody backup you in future for such cases?
          Hide
          Permalink
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          manifests/cucumber.pp
          http://jenkins-ci.org/commit/infra-puppet/a428f4efe4d8bf21b386d98fadad52a126a323c3
          Log:
          INFRA-240 auto-restart SLAPD

          To feed a new SSL certificate automatically to LDAP daemon, just
          auto-restart it every day. The time chosen is the off-business hour for
          America and Europe.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: manifests/cucumber.pp http://jenkins-ci.org/commit/infra-puppet/a428f4efe4d8bf21b386d98fadad52a126a323c3 Log: INFRA-240 auto-restart SLAPD To feed a new SSL certificate automatically to LDAP daemon, just auto-restart it every day. The time chosen is the off-business hour for America and Europe.
          Hide
          Permalink
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: R. Tyler Croy
          Path:
          manifests/cucumber.pp
          http://jenkins-ci.org/commit/infra-puppet/dcda4f5ecbc804816abb7ad7bf55a3b669203e8a
          Log:
          Merge pull request #70 from kohsuke/master

          INFRA-240 auto-restart SLAPD

          Compare: https://github.com/jenkinsci/infra-puppet/compare/e590d8f520f7...dcda4f5ecbc8

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: R. Tyler Croy Path: manifests/cucumber.pp http://jenkins-ci.org/commit/infra-puppet/dcda4f5ecbc804816abb7ad7bf55a3b669203e8a Log: Merge pull request #70 from kohsuke/master INFRA-240 auto-restart SLAPD Compare: https://github.com/jenkinsci/infra-puppet/compare/e590d8f520f7...dcda4f5ecbc8
          Hide
          Permalink
          kohsuke Kohsuke Kawaguchi added a comment -

          This ticket started a discussion in the dev list.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - This ticket started a discussion in the dev list .

            People

            • Assignee:
              kohsuke Kohsuke Kawaguchi
              Reporter:
              orrc Christopher Orr
            • Votes:
              13 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: