Hello,
I am experiencing issues with Maven package management for my project on the GitLab Free Tier. Despite having a valid Personal Access Token (PAT) with the correct scopes, I am encountering errors related to package management endpoints and functionalities. So, I’m unable to deploy or fetch any GitLab package from our Maven Java applications. I would appreciate your assistance in resolving these issues.
Details of the Issue
I am unable to access the Maven Package Registry endpoints for my project. Specifically, I am encountering errors such as:
{“error”:“package_id is invalid”} 404 Not Found or similar errors when attempting to interact with /packages/maven/ or /packages/generic/ endpoints.
Request for Assistance
Could you please assist with the following:
-
Verify Maven Package Registry Availability: Please confirm whether the Maven Package Registry endpoints are available on the GitLab Free Tier for my project or if there are known issues affecting these endpoints.
-
Alternative Solutions: If Maven Package Registry is not available on the Free Tier, could you provide guidance on how I can manage Maven packages effectively? Are there alternative endpoints or methods for managing Maven artifacts on the Free Tier?
-
Troubleshooting Steps: If there are any additional troubleshooting steps or configurations that I should be aware of for using the Maven Package Registry or Generic Package Registry, please provide details.
Settings Used
in pom.xml file:
<repositories>
<repository>
<id>gitlab-maven</id>
<url>https://gitlab.com/api/v4/groups/12345/-/packages/maven</url>
</repository>
</repositories>
<distributionManagement>
<repository>
<id>gitlab-maven-ci</id>
<url>${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/maven</url>
</repository>
<snapshotRepository>
<id>gitlab-maven-ci</id>
<url>${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/maven</url>
</snapshotRepository>
</distributionManagement>
in settings.xml file:
<servers>
<server>
<id>gitlab-maven</id>
<configuration>
<httpHeaders>
<property>
<name>Private-Token</name>
<value>${GITLAB_READ_API_TOKEN}</value>
</property>
</httpHeaders>
</configuration>
</server>
</servers>
Note: The token has the required scopes, and it works normally