AMPS run fails / stuck on downloading atlassian-plugin-sdk-tgz

Bitbucket Development Bitbucket Server
1

Hi

Our CI server started to fail builds / timeout. It fails build with:

[ERROR] Failed to execute goal com.atlassian.maven.plugins:bitbucket-maven-plugin:8.3.1:debug (default-cli) on project parent: Execution default-cli of goal com.atlassian.maven.plugins:bitbucket-maven-plugin:8.3.1:debug failed: java.io.IOException: Server returned HTTP response code: 401 for URL: https://marketplace.atlassian.com/rest/1.0/plugins/atlassian-plugin-sdk-tgz

That https://marketplace.atlassian.com/rest/1.0/plugins/atlassian-plugin-sdk-tgz URL indeed doesn’t answer at the moment. I’ve figured out that this is part of some periodic ‘update’ check.

Is there a way do disable this check on CI? We preferably just want the version(s) we specified and not ad-hock checking of additional resources?

At the moment this fails all our CI builds =(.

2

Apparently the marketplace was down, which also brought AMPS down with it.

It would be still nice to be able to suppress this check in a CI build.

3

Bump.

I’ve gotten bitten by this again.
Seems to work locally, but fails on the build server.

So, this download seems to be cached. But not sure where / how that caching works.
I really loved to disable this dependency on the Atlassian servers

Update: In the code there seems to be a .skipCheck flag, but could not
figure out yet how to actually set it.

Another thin I’ve found it: the maven plugin writes into the Java Preferences if it did the
check and then skips it. Grr

Best regards
Roman Stoffel

4

You can prevent the update check by adding the following in your jira-maven-plugin configuration in pom.xml:

<skipAllPrompts>true</skipAllPrompts>

1 Like