End to End kyma test for node and maven

[MrShubham22]

DOCKER_PASSWORD github secret in this repo needs to be changed for the e2e tests to work

[cla-assistant]

All committers have signed the CLA.

[chgeo]

@MrShubham22 please send the secret to me via Teams

[MrShubham22]

@MrShubham22 please send the secret to me via Teams

done

[chgeo]

2 things from my side:

Lots of redundancies between the Node and Java scripts. Have you thought about reusing common parts? See e.g. how CF deployment reuses code through actions.

Lots of lengthy 'progress log', which should be avoided. Especially docker, and curl cause this. Check for options in these tools that hide progress output. I have done this already for mvn via its -B parameter.

[MrShubham22]

2 things from my side:

Lots of redundancies between the Node and Java scripts. Have you thought about reusing common parts? See e.g. how CF deployment reuses code through actions.

Lots of lengthy 'progress log', which should be avoided. Especially docker, and curl cause this. Check for options in these tools that hide progress output. I have done this already for mvn via its -B parameter.

Sure will look into that , Thanks

[uwe-klinger]

Ok, from testing perspective. Please see Christian's comments.

[MrShubham22]

2 things from my side:

Lots of redundancies between the Node and Java scripts. Have you thought about reusing common parts? See e.g. how CF deployment reuses code through actions.

Lots of lengthy 'progress log', which should be avoided. Especially docker, and curl cause this. Check for options in these tools that hide progress output. I have done this already for mvn via its -B parameter.

tried moving the common docker login and setting up env part of a diff workflow but docker login and kubeconfig export and whatever setup we do , the context of it gets lost when we come back to the called workflow and based on that login and kubeconfig exported file we're pushing images.

[MrShubham22]

2 things from my side:

Lots of redundancies between the Node and Java scripts. Have you thought about reusing common parts? See e.g. how CF deployment reuses code through actions.

Lots of lengthy 'progress log', which should be avoided. Especially docker, and curl cause this. Check for options in these tools that hide progress output. I have done this already for mvn via its -B parameter.

also yes i'm looking for -quiet verbose for the cli commands wehrever possible