-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maven package ecosystem not checking dependencies from my private repo #5523
Comments
I trust the dependabot is not able to connect to my internal maven repo but I can't see any authentication error or timeout |
Is this a duplicate of #2291? |
I believe you need a |
Hi, @pavera thanks for your reply. Do you mean ? <parent>
<groupId>my.internal.groupId</groupId>
<artifactId>internal-parent</artifactId>
<version>1.5.0</version>
<relativePath/> <!-- lookup parent from repository -->
</parent> Kind regards, |
@gianielsevier I just deployed #5884 if you would like to manually trigger a run to see if it is fixed now. |
Ah, I see what you are saying now. This call is timing out:
But we don't see the stack because the job ends too quickly. I've been testing timeout issues internally and the stack often comes several minutes after the initial call. |
Hi, @jakecoffman thanks for working on this issue. I'll try to run it again |
@gianielsevier any update? |
Package ecosystem
maven
Package manager version
3.8.6
Language version
java11, java17
Manifest location and content before the Dependabot update
pom.xml
If using GitHub-native Dependabot, attach your dependabot.yml file or provide a link to it
What you expected to see, versus what you actually saw
I was expecting dependabot check dependencies from my private maven repo. But it is going to repo.maven.apache
Native package manager behavior
🕹 Bonus points: Smallest manifest that reproduces the issue
The text was updated successfully, but these errors were encountered: