-
Notifications
You must be signed in to change notification settings - Fork 356
Jitpack not working as expected #4998
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
Comments
Strange. It works for me:
Maybe your failure is related to the registry or any other cause. Have a look at the Camel Integration troubleshooting guide. |
Is there a way to see any more detailed error message than the following?
It only happens when I try to run the Jitpack example. Is it possible that the registry issue only affects Jitpack example? With Jitpack (Failure)
Without Jitpack (Success)
Any other info is much appreciated! |
The guide I've provided above [1] should give you more details on how to troubleshoot an Integration. In your case what is clearly happening is a Maven build failure. I guess there could be some problem accessing the Jitpack repository by your cluster. You can have a more detailed trace checking the log of the Camel K operator Pod ( [1] https://camel.apache.org/camel-k/2.1.x/troubleshooting/troubleshooting.html |
Thank you for the clue! It seems my setting.xml uses company Nexus server as proxy. To make it work, I had to add the following to Maven
It'll make Jitpack related dependencies go around company Nexus. However, we can also do it the proper way -- that is make company Nexus server support Jitpack See: jitpack/jitpack.io#506 (comment) Thank you @squakez I think we can close this issue? |
What happened?
When running the example code of Jitpack (https://github.com/apache/camel-k-examples/tree/main/generic-examples/jitpack)
It seemed the integration always goes into Error status without clear error message.
I looked up the status of several components, but couldn't figure out why it failed...
Steps to reproduce
Just follow the steps in the Jitpack example from camel-k examples github
Relevant log output
Camel K version
╰─ kamel version
Camel K Client 2.1.0
The text was updated successfully, but these errors were encountered: