René Dupont

I'm encountering it as well `java.io.IOException: Cannot use custom test directory 'docker/build/test-results/test' that does not exist!` but only for reruns of the pipeline (without any changes to the code) so...

@clemensutschig I assume that error occurs in my case because the custom test dir (with reports as content) is normally being created during the build stage which is never happening...

@clemensutschig Yes, true :). I am not understanding yet though why this test-results stashing is happening at that point at all. There won't be anything in that folder to stash...

Sounds good 👍🏻. Just thinking about the case where someone misconfigured the build by putting the test-results neither in the default nor a custom dir... should the pipeline fail in...

adding one of your ideas discussed in the past on how to tackle this: > we could take the list of valid project/namespaces from openshift and display them in the...

Closing this as using git commit tag as image tag is by now the default way when using helm in ods. See related issue #1027

Yes, therefore I'd suggest to keep that workaround of switching back to java 11 after the gradle build in the readme/docs regarding using java 17 as long as sonarqube does...

I guess this was fixed by now with this line: https://github.com/opendevstack/ods-quickstarters/blob/4.x/be-java-springboot/Jenkinsfile.template#L29 I close this @braisvq1996

For gradle, you can add a `gradle.properties` with the nexus settings of your ocp cluster to your local `.gradle` folder and it will be picked up by gradle for any...

I tried a few things today and came up with a possible solution, before creating a draft PR I'd like to have feedback and start discussing possible other options/improvements. My...