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

Restore jep-229 builds

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi

      JEP-229 releases are still not working, I assume something was done in artifactory to block them?

      I believe Daniel Beck is the only one with access here?
      https://github.com/jenkinsci/azure-vm-agents-plugin/runs/3548700870?check_suite_focus=true

      cc Mark Waite Gavin Mogan Olivier Vernin

        Attachments

          Issue Links

            Activity

            Show
            jglick Jesse Glick added a comment - https://github.com/jenkins-infra/jenkins-maven-cd-action/pull/9
            Hide
            jglick Jesse Glick added a comment -

            Looks like the trick worked.

            I guess we can make this change permanent even after JFrog restores basic auth? Since my reading of https://www.jfrog.com/confluence/display/JFROG/Access+Tokens#AccessTokens-AuthorizationHeaders is that this is the preferred mode.

            Show
            jglick Jesse Glick added a comment - Looks like the trick worked. I guess we can make this change permanent even after JFrog restores basic auth? Since my reading of https://www.jfrog.com/confluence/display/JFROG/Access+Tokens#AccessTokens-AuthorizationHeaders is that this is the preferred mode.
            Hide
            jglick Jesse Glick added a comment -

            (We could continue defining MAVEN_USERNAME from RPU, for the benefit of repositories using older versions of the action.)

            Show
            jglick Jesse Glick added a comment - (We could continue defining MAVEN_USERNAME from RPU, for the benefit of repositories using older versions of the action.)
            Hide
            danielbeck Daniel Beck added a comment -

            JFrog followed up with my support request and asked questions. They said it's likely because the token user name is not all lowercase, a known issue.

            However, I wasn't able to reproduce the problem this morning, i.e. basic auth seems to work again. I responded with that information, let's see where this goes.

            So as of right now, both old and new actions should be working.

            Show
            danielbeck Daniel Beck added a comment - JFrog followed up with my support request and asked questions. They said it's likely because the token user name is not all lowercase, a known issue. However, I wasn't able to reproduce the problem this morning, i.e. basic auth seems to work again. I responded with that information, let's see where this goes. So as of right now, both old and new actions should be working.
            Hide
            jglick Jesse Glick added a comment -

            OK. I see no need to roll anything back; the bearer token seems generally preferable.

            Show
            jglick Jesse Glick added a comment - OK. I see no need to roll anything back; the bearer token seems generally preferable.

              People

              Assignee:
              danielbeck Daniel Beck
              Reporter:
              timja Tim Jacomb
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: