-
Notifications
You must be signed in to change notification settings - Fork 1
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
The test pipeline should also perform deployment #15
Comments
So it will be needed that we set different values such as:
NOTE: Pod created could fail if the backend system required (postgresql, etc) is not available. So do we plan to also manage the |
Test 1I don t see a deployment yaml created within the namespace running the tekton task "deploy". Log just reports
Test 2I executed a new pipelineRun and now I can see the resources deployed. FYI: I passed as param
|
Question: As |
FYI. If we trigger a build - https://console-openshift-console.apps.qshift.snowdrop.dev/k8s/ns/test2/builds/quarkus-helloworld-1 the resulting image build fails to start from the pod
Here is the log of the s2i build
NOTE: Red Hat documentation don't use |
…on ocp. #15 Signed-off-by: cmoulliard <[email protected]>
Build issue fixed after I changed the maven parameters to perform the build using docker and not s2i
|
We could possibly live without the registry and credentials and default to the internal registry for now (unless it requires very low effort). Reagrding |
I agree with you as tekton task (= mvn package -Dquarkus.container-image.push=true) works using internal registry ;-) |
…on ocp. #15 Signed-off-by: cmoulliard <[email protected]>
Can we close this issue ? @iocanel |
The pipeline currently performs a simple maven build.
It would be create if we had a deployment step.
The deployment step could just use
./mvnw quarkus:deploy -Dquarkus.openshift.deploy=true
or something like this.The text was updated successfully, but these errors were encountered: