After creating a support ticket, the issue has been fixed by Atlassian. Guess they had some misconfiguration or hickups in there infrastructure. Sadly support didn’t provide any information about what was actually wrong.
Because the actual fix from Atlassian took some time, we used following settings.xml as a workaround
<settings>
<profiles>
<profile>
<id>atlassian-proxy-alternative</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>atlassian-public</id>
<url>https://packages.atlassian.com/mvn/maven-external/</url>
</repository>
<repository>
<id>atlassian-plugin-sdk</id>
<url>file://${env.ATLAS_HOME}/repository</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>atlassian-public</id>
<url>https://packages.atlassian.com/mvn/maven-external/</url>
</pluginRepository>
<pluginRepository>
<id>atlassian-plugin-sdk</id>
<url>file://${env.ATLAS_HOME}/repository</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
</settings>
bitbucket-pipelines.yml for reference
image: eclipse-temurin:17-alpine
pipelines:
default:
- parallel:
- step:
name: Build and Test
caches:
- maven
script:
# Set ATLAS_VERSION
- export ATLAS_VERSION=9.1.1
# Set ATLAS_HOME
- export ATLAS_HOME=/opt/atlassian-plugin-sdk-${ATLAS_VERSION}
# Download Atlassian SDK
- wget https://packages.atlassian.com/mvn/maven-external/com/atlassian/amps/atlassian-plugin-sdk/${ATLAS_VERSION}/atlassian-plugin-sdk-${ATLAS_VERSION}.tar.gz -O - | tar -C /opt -xvzf -
# Build
- ${ATLAS_HOME}/bin/atlas-mvn -s settings.xml -B clean deploy