Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-1098

403 errors for GitHub actions accessing org.wildfly.legacy.test artifacts

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • Q1CY26
    • None
    • None
    • None
    • MWES 2026-01-20

      rh-ee-msappegr reports:

      In GitHub actions I can see many failures (WildFly PRs):

      e.g.

      69 Error: Failed to execute goal on project wildfly-naming: Could not collect dependencies for project org.wildfly:wildfly-naming:jar:40.0.0.Beta1-SNAPSHOT
      Error: Failed to read artifact descriptor for org.wildfly.legacy.test:wildfly-legacy-spi:jar:10.0.2.Final
      Error: Caused by: The following artifacts could not be resolved: org.wildfly.legacy.test:wildfly-legacy-spi:pom:10.0.2.Final (absent): Could not transfer artifact org.wildfly.legacy.test:wildfly-legacy-spi:pom:10.0.2.Final from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): status code: 403, reason phrase: Forbidden (403)
      Error: Failed to read artifact descriptor for org.wildfly.legacy.test:wildfly-legacy-versions:jar:10.0.2.Final
      Error: Caused by: The following artifacts could not be resolved: org.wildfly.legacy.test:wildfly-legacy-versions:pom:10.0.2.Final (absent): Could not transfer artifact org.wildfly.legacy.test:wildfly-legacy-versions:pom:10.0.2.Final from/to jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/): status code: 403, reason phrase: Forbidden (403)
      Error: -> [Help 1]
      

      From PR https://github.com/wildfly/wildfly/actions/runs/21286284689/job/61268167735?pr=19547 and other PRs too.

      At this moment, looking at https://github.com/wildfly/wildfly/actions it looks like all the recent jobs that pull this artifact are failing. (There are green jobs there but they don't pull this artifact.)

      I haven't tested a local build to see if it happens. WildFly's TeamCity server has it's own local repository acting as a cache so it's not affected.

              dhladky@redhat.com David Hladky
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: