Hi!
Since Friday our build pipelines fail with the following exception:
Failed to collect dependencies at com.aspose:aspose-words:jar:jdk17:22.3: Failed to read artifact descriptor for com.aspose:aspose-words:jar:jdk17:22.3: Could not transfer artifact com.aspose:aspose-words:pom:22.3 from/to AsposeJavaAPI (https://repository.aspose.com/repo/
): authorization failed for https://releases.aspose.com/words/java/, status: 403 Forbidden
Nothing changed on our side.
If I look at https://status.aspose.com/, it says “repository.aspose.com is down since 18/11/2022 13:53:46 UTC”. Do we know when it will be back up?
Kind regards
@svanloon
Our Java repository URL changed to https://releases.aspose.com/java/repo/.
<repositories>
<repository>
<id>AsposeJavaAPI</id>
<name>Aspose Java API</name>
<url>https://releases.aspose.com/java/repo/</url>
</repository>
</repositories>
Kindly update your project settings accordingly. Feel free to reach if you still face any issue related to it. Thanks.
Hi @farooq.sheikh,
I’m afraid this doesn’t solve the issue. Retrieving it locally works via both urls. When we try to build via a Linux agent, it fails with thesame exception:
Failed to collect dependencies at com.aspose:aspose-words:jar:jdk17:22.3: Failed to read artifact descriptor for com.aspose:aspose-words:jar:jdk17:22.3: Could not transfer artifact com.aspose:aspose-words:pom:22.3 from/to AsposeJavaAPI (https://releases.aspose.com/java/repo/
): authorization failed for https://releases.aspose.com/words/java/, status: 403 Forbidden
Kind regards
@svanloon
Kindly confirm which infrastructure are you using Azure Devops / Github Actions or others? So i can forward this request to our hosting team. Thanks.
@farooq.sheikh
We use standardised azure VM Scale Sets based on official Microsoft Hosted Agents, our agents, run in Azure and have full access to internet:
https://github.com/actions/runner-images/blob/main/images/linux/ubuntu1804-readme.md
Every build we start with a clean agent so nothing is cached.
@svanloon Thank you for additional information. We are working on the issue and let you know once it is resolved.
@svanloon
Can you please re-run and verify as our hosting team updated their ACL rules. Thanks.
@alexey.noskov FYI.
2 Likes