We need to bind these parameters to values received from webhook
We need to set custom interceptors to filter webhooks
Maven build needs more pod resource than default setting, mounting of settings.xml, and pvc volumes (e.g., I have been using a pvc to cache artifactory repo) - hence need to be able to have more customizations for Task objects
Added ability to switch service accounts between tasks
I started working on an example - it reacts to open/reopen pull_request gets url/commit sha from the webhook, and passes these to git-clone ClusterTask and does a maven build, then the image is build using .war generated from maven step via ocp cli ClusterTask, it is deployed in test and we subsequently run python integration tests against it with a comment being posted against the PR that contains pytest logs
…m webhook
We need global pipeline parameters that can be set via webhook trigger and shared by the tasks - hence add pipeline_params https://tekton.dev/docs/pipelines/pipelines/#specifying-parameters
We need to bind these parameters to values received from webhook
We need to set custom interceptors to filter webhooks
Maven build needs more pod resource than default setting, mounting of settings.xml, and pvc volumes (e.g., I have been using a pvc to cache artifactory repo) - hence need to be able to have more customizations for Task objects
Added ability to switch service accounts between tasks
I started working on an example - it reacts to open/reopen pull_request gets url/commit sha from the webhook, and passes these to git-clone ClusterTask and does a maven build, then the image is build using .war generated from maven step via ocp cli ClusterTask, it is deployed in test and we subsequently run python integration tests against it with a comment being posted against the PR that contains pytest logs