We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Artifactory
While looking at jenkinsci/jenkins#10036 it appears that there are various releases in https://repo.jenkins-ci.org/public/com/github/eirslett/frontend-maven-plugin/ which do not exist in the central repository: https://repo.maven.apache.org/maven2/com/github/eirslett/frontend-maven-plugin/
Due to this, renovate keeps picking up release builds you cannot find in the proper development repository.
Where are these builds coming from and how can we get a rid of them?
No response
The text was updated successfully, but these errors were encountered:
@NotMyFault does it work if you specify, in your Renovabot setup, first the Central then Jenkins repos (ref. https://docs.renovatebot.com/configuration-options/#registryurls) ?
Sorry, something went wrong.
@NotMyFault does it work if you specify, in your Renovabot setup, first the Central then Jenkins repos (ref. docs.renovatebot.com/configuration-options#registryurls) ?
Unfortunately, I have no time to investigate into that atm, but it affects dependabot too jenkinsci/jellydoc-maven-plugin#129
No branches or pull requests
Service(s)
Artifactory
Summary
While looking at jenkinsci/jenkins#10036 it appears that there are various releases in https://repo.jenkins-ci.org/public/com/github/eirslett/frontend-maven-plugin/ which do not exist in the central repository: https://repo.maven.apache.org/maven2/com/github/eirslett/frontend-maven-plugin/
Due to this, renovate keeps picking up release builds you cannot find in the proper development repository.
Where are these builds coming from and how can we get a rid of them?
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: