squakez commented on PR #954: URL: https://github.com/apache/camel-k-runtime/pull/954#issuecomment-1404701149
Yeah, that's the reason I proposed you to prepare both Camel K runtime and Camel K developments locally before pushing the related PRs. When I need something that affects both projects, the approach I use is the following one: * I develop the change in Camel K runtime locally. I make sure a test can cover the change (btw, this may me something to work on as well). * I do the change in Camel K project. I prepare an E2E test to make sure my change is okey (in this case it could be creating a Java native example) * I prepare my local environment to push an image to my local kubernetes cluster (minikube): https://camel.apache.org/camel-k/next/contributing/e2e.html#testing-operator - when you `make images CAMEL_K_RUNTIME_DIR=/path/to/camel-k-runtime-project` (this path has to point to your Camel K runtime project with the changes done in step 1), an image with both the Camel K and Camel K runtime (both snapshot) latest developments will be pushed to the registry * Now, if you run the test, it will run against the image done in previous step, making sure that both developments are good to go * Separately you can issue the PR for both Camel K and Camel K Runtime In this way we minimize the risk to do some development on the runtime that is not yet ready in Camel K, just doing one thing at a time. Let me know if I can help to make this approach working for you as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
