-
Notifications
You must be signed in to change notification settings - Fork 17
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
Replace Java dependencies with as many Red Hat built ones #262
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Pierangelo Di Pilato <[email protected]>
Signed-off-by: Pierangelo Di Pilato <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pierDipi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Pierangelo Di Pilato <[email protected]>
) | ||
|
||
func main() { | ||
metadata, err := maven.ScrapRedHatMavenRegistry(maven.RedHatMavenGA) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's only Quarkus version, we might be good with:
➜ ~ curl -s "https://code.quarkus.redhat.com/api/platforms" | jq -r '.platforms[0].streams[0].releases[0].version'
3.8.5.SP1-redhat-00001
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SP1 is actually newer than 3.8.5.redhat-00003
. Where regular 3.8.5 is standard release. Then SP1 stands for security patch 1 of 3.8.5 I believe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SP == service patch, sorry :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's only Quarkus version, we might be good with:
no, it's not only for Quarkus, see the list in the diff in the PR body
SP1 is actually newer than 3.8.5.redhat-00003. Where regular 3.8.5 is standard release. Then SP1 stands for security patch 1 of 3.8.5 I believe.
hmm, aren't versions here sorted ? https://maven.repository.redhat.com/ga/com/redhat/quarkus/platform/quarkus-bom/maven-metadata.xml
Also latest
says 3.8.5.redhat-00003
and not the SP
one
<latest>3.8.5.redhat-00003</latest>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are not unfortunately. The service patch actually might be fixing Quarkus platform libs etc, but core quarkus is not changing. Hence the prefix version stays the same, and the rest is incrementing very "naturally".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, ok, I think this is already better than what we currently have in Konflux builds, so special sorting can be added later or we can always add "bump dependencies" using other tools later (like renovate or dependabot)
3a8988c
to
51a852c
Compare
Signed-off-by: Pierangelo Di Pilato <[email protected]>
return fmt.Errorf("failed to update pom file %q: %w", p, err) | ||
} | ||
|
||
commitMsg := fmt.Sprintf("[%s] Updated POM file %s with Red Hat dependencies", branchName, p) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
commitMsg := fmt.Sprintf("[%s] Updated POM file %s with Red Hat dependencies", branchName, p) | |
commitMsg := fmt.Sprintf("[%s] Updated POM file %s with Red Hat dependencies", targetBranch, p) |
Shouldn't really make a difference here, but theoretically on "release-next" we'd push to main
Putting some thoughts around version in pom. I'm pretty sure that importing BOM in Maven project should mean that version provided by the BOM are considered "managed". Therefore project pom.xml doesn't have to redeclare In theory EKB data-plane should work just by using Quarkus' BOM and version will be inherited from it. I'll try to play with it a bit. |
@dsimansk any news for the last comment? |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@dsimansk any news? we need this one in some shape or form |
@creydr I guess you had comments, can you write them here? |
My main thought about this was, if we could integrate this into the update-to-head jobs, so we have this tested also somehow in CI (no need to do this in this PR) |
How is this solved in other repos? Do people scrape deps? |
In the old system there is a EAP based Java service but requires EAP to run and there is not alternatives for Konflux, the JBS in Konflux is beeing redesigned but it's not there yet |
We discussed why in the past, I lost the links to the existing tools now :) |
So people will do scraping in each repo that has java deps for now? Interesting. |
No, scraping is an alternative to doing it manually |
Example diff for the current pom.xml for EKB 1.15
and it also builds successfully: