search

siamaksade / tekton-cd-demo

CI/CD demo with Tekton on OpenShift
62 stars 93 forks source link

OpenShift Pipeline 1.4 issues #11

Open rbaumgar opened 3 years ago

rbaumgar commented 3 years ago

In the eventlistener the trigger name has now "ref" as label (old name). The eventlistener now runs on 8000 (old 8080). triggers/eventlistener.yaml

...
      template:
        ref: petclinic-trigger-template
...
  port:
    targetPort: 8000
...

When you upgrade to 1.4 the eventlistener still has the wrong label for the template. Big troubles when you want to update/remove! So uninstall this example before upgrade.

rbaumgar commented 3 years ago

see https://tekton.dev/docs/triggers/eventlisteners/#syntax

jkeam commented 3 years ago

@rbaumgar Were you able to get the pipeline to successfully complete using 1.4? My tasks fail and I'm not sure why, for example, the unit-tests task.

Failing Event:

"step-mvn-goals" exited with code 255 (image: "gcr.io/cloud-builders/mvn@sha256:627850e2b75ed05a87ab16ace56e36e457d488836817fd94cf4f0287a78d31f9"); for logs run: kubectl -n demo-cicd logs petclinic-deploy-dev-8051qo-unit-tests-rssx9-pod-xwqgf -c step-mvn-goals

Last lines of pod logs:

:: Built with Spring Boot :: 2.2.5.RELEASE

2021-04-28 12:56:28.912  INFO 92 --- [           main] o.s.s.p.owner.PetControllerTests         : Starting PetControllerTests on petclinic-deploy-dev-8051qo-unit-tests-rssx9-pod-xwqgf with PID 92 (started by root in /workspace/source/spring-petclinic)
2021-04-28 12:56:28.914  INFO 92 --- [           main] o.s.s.p.owner.PetControllerTests         : The following profiles are active: default

Logs look ok to me, even running the task locally appears to work just fine:

 docker run --rm -v $(pwd):/test -it gcr.io/cloud-builders/mvn:3.5.0-jdk-8 validate -f test/pom.xml
rbaumgar commented 3 years ago

no, pipeline does not run. Always a problem in code-analysis and unit tests. But every time I install failure with a different class. e.g.

step-mvn-goals" exited with code 1 (image: "gcr.io/cloud-builders/mvn@sha256:af4dc16ce539f77e1ae897165c63711d14e1f666389030d231c082f41f03f9bf"); for logs run: kubectl -n tekton-cicd logs petclinic-deploy-dev-h4hxb-code-analysis-5tvbz-pod-6r9g6 -c step-mvn-goals

pod log

Failed to execute goal on project spring-petclinic: Could not resolve dependencies for project org.springframework.samples:spring-petclinic:jar:2.2.0.BUILD-SNAPSHOT: 
Failed to collect dependencies at org.springframework.boot:spring-boot-starter-test:jar:2.2.5.RELEASE -> com.jayway.jsonpath:json-path:jar:2.4.0 -> net.minidev:json-smart:jar:2.3 -> net.minidev:accessors-smart:jar:1.2
Failed to read artifact descriptor for net.minidev:accessors-smart:jar:1.2: Could not transfer artifact net.minidev:accessors-smart:pom:1.2 from/to nexus (http://nexus:8081/repository/maven-public/): /workspace/source/.m2/net/minidev/accessors-smart/1.2/accessors-smart-1.2.pom.part (No such file or directory)
rbaumgar commented 3 years ago

see https://github.com/siamaksade/tekton-cd-demo/pull/12