5. Pipeline tasks - CI/CD with Tekton & ArgoCD

[@palanisamy-dl9qe]

Thanks for effort, just one question why do we pass the git revision as parameter, do we need pass the git commit version somewhere or it will automatically fetch from github page inside coffee testing app.

[@SebastianDaschnerIT]

Just a preference, that would work too of course

[@tamilselvan8343]

Hi @Sebastian. Why dont we pass the name and value pairs of build inputs in pipeline crd instead of pipelinerun?Can you please elaborate.

[@SebastianDaschnerIT]

We want to dynamically pass these values, so that they can be defined in the individual runs. Of course one could also refactor the examples, e.g. make the Git URL hardcoded and only provide the commit revision, etc.

[@tamilselvan8343]

@@SebastianDaschnerIT Correct .my question is why dont we pass the parameter values on pipelinerun-.it should apply pipeline and internally apply task and steps.

[@SebastianDaschnerIT]

Sorry, I don't understand the question. We are passing the parameters in the pipelinerun. My example shows this also in the code here: github.com/sdaschner/coffee-testing-config/tree/master/pipelinerun which can be executed manually or via GitHub trigger: github.com/sdaschner/coffee-testing-config/tree/master/pipelinetriggers which takes the information of the Git commit & push.

[@tamilselvan8343]

@@SebastianDaschnerIT why we are passing the parameters inside pipeline crd/kind? We declared all values in pipelinerun as generically . if we call${params.buildversion} it would fetch values from pipelinerun right.

[@SebastianDaschnerIT]

Ah, yes correct :) In my example some values are just hardcoded, but that's just the example, you could call all of them dynamically if you wanted, right.

[@AlexSurf2008]

Thanks for sharing Sebastian!

[@rogeriosilvarocha]

Nice! Thanks!!!

[@palanisamy-dl9qe]

Hi @sebastian localhost:8001/q/health i could see database connections health check-up and running. org.hibernate.exception.SQLGrammarException: JDBC exception executing SQL [select o1_0.id,o1_0.origin_name,o1_0.status,o1_0.type from orders o1_0] [ERROR: relation "orders" does not exist Position: 60] [n/a]Error id 9bbda07c-1a56-4144-ad85-9202cbc076ef-11

[@SebastianDaschnerIT]

The default config in the Git branch should create the database schema and load the load-data.sql file on application startup (see repository). Are you sure the configuration is correct and hasn't been changed?

[@palanisamy-dl9qe]

@@SebastianDaschnerIT Thanks for quick help. I could see /src/main/resources/scripts contains load-data.sql file. + podman run -d --rm --name coffee-shop-db --network kind -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -v /c/Users/User/coffee-testing-master/coffee-shop/src/main/resources/scripts:/scripts:ro postgres e3963ab61352e39b85d59e98267df454e616edf1bc47637414694e80c8f60510

[@SebastianDaschnerIT]

No, the application applies the script to the database, it doesn't have to be added to the db container

[@palanisamy-dl9qe]

@@SebastianDaschnerIT ​ @Sebastian Daschner Thanks again. correct first I executed the file name called local-build.sh which contains the build for the application and it will prepare the target and create a docker image. Next, I have executed another file local-run-env.sh which will help us use the previous image created using local-build.sh script will then start the container coffee-shop app, DB, Db. Would you like me to change anything else for the local build and test? because when I see the build log db files are loading from my local path instead of the container + podman run -d --rm --name coffee-shop-db --network kind -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -v /c/Users/User/coffee-testing-master/coffee-shop/src/main/resources/scripts:/scripts:ro postgres 4402db0d60845e9b9d095c456eaeaf1fba841f58730dca35b2148e748083a835