Unable to let my action build download one of my github package

[mimir234]

Select Topic Area

Question

Body

Hi everybody

I'm facing a pretty dumb issue I think, but i didn't find a way to fix it

I have two repos maven/java :

• the first one is a library that is automatically built and deployed into github packages repository
• the second one is an application which has the first as a dependency

The problem that I'm facing is that my action build of my second repo failes to download the first repo package.
The maven build has an 401 unauthorized responses from github package repository.

I've tried to define the action build like the following :

- name: Build with Maven
  run: mvn -B package --file pom.xml -s $GITHUB_WORKSPACE/settings.xml
  env:
    GITHUB_TOKEN: ${{ github.token }}

but it doesn't fix the issue

I know that the fix should be very simple but I'm not able to find out the solution by myself. May you please indicate the apropriate way to do ?

[nirav-gajera]

try:

name: Build with Maven
on:
  push:
    branches:
      - main
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v2
      - name: Build with Maven
        run: mvn -B package --file pom.xml -s $GITHUB_WORKSPACE/settings.xml
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

[TomVanWemmel]

The value of {{secrets.GITHUB_TOKEN}} needs to be a personal access token from you or another user within your organisation.

Sharing packages between (private) repos has been requested multiple times and is even part of the roadmap. Currently it says Q2 2023, but the issue is still unresolved...
github/roadmap#578

EDIT: I looked at your repository and you probably need to add the following repository to your maven settings (do change the name of the organisation)

<repository>
    <id>github</id>
    <url>https://maven.pkg.github.com/<INSERT_ORGANISATION>/*</url>
    <snapshots>
        <enabled>true</enabled>
    </snapshots>
</repository>

[mimir234]

Thank you for your help @TomVanWemmel

Yeah I configured the repository in my maven pom.xml file https://github.com/garganttua/garganttua-server-distribution-maker/blob/main/pom.xml

here is my file :


github garganttua server distribution maker
github garganttua server distribution maker
https://maven.pkg.github.com/garganttua/garganttua-server-distribution-maker


github garganttua server distribution maker
github garganttua server distribution maker
https://maven.pkg.github.com/garganttua/garganttua-server-distribution-maker

<repositories>
	<repository>
		<id>github garganttua server core</id>
		<name>github garganttua server core</name>
		<url>https://maven.pkg.github.com/garganttua/garganttua-server-core</url>
		<snapshots>
			<enabled>true</enabled>
		</snapshots>
	</repository>
</repositories>

but the action is still not working and my repositories are "public"

[TomVanWemmel]

If your packages are public, I think you can just run

- name: Build with Maven
  run: mvn -B package --file pom.xml

Because the basic config would create a settings.xml file in the default maven folder (~/.m2)
See setup-java.

You could try debugging the actions by defining a variable ACTIONS_RUNNER_DEBUG with value true.
Or adding steps in between to verify that the settings contain the desired values.

- name: Show file content
  run: cat ~/.m2/settings.xml

[mrvamsidhar-ais]

Any luck?

[BastianTrifork]

I am facing the same issue.
I have the same setup as @mimir234, and 2 days ago all my pipelines stopped working, since maven got a 401 when pulling the package from the other repository.

I have double checked that my token is up-to-date and valid, it is the same one i use to pull locally, so I've verified that it is not the token that is at fault.
I can also see the package it is attempting to pull is alive and well in ghcr, so that shouldn't be an issue either.

I still get a 401 Unauthorized when trying to pull my own package, and its driving me nuts!

Various websites have recommended using "s4u/maven-settings-action@v2", however, due to company policy, i can't use unverified third party actions.

Has anyone experienced this issue too (and if so, how did you work around it)?