Skip to content

Latest commit

 

History

History
82 lines (54 loc) · 3.22 KB

InstallNightlyBuild.md

File metadata and controls

82 lines (54 loc) · 3.22 KB

Nightly builds



The Tekton Webhooks Extension has a hosted image of the latest builds located at gcr.io/tekton-nightly/extension.

Note: If you want to install into an alternative namespace you would need to modify all namespace entries in the applied yaml files.

  • To install the latest nightly image:

    1. Clone this repository

      git clone https://github.com/tektoncd/experimental.git
    2. Change into the webhooks-extension directory

      cd webhooks-extension
    3. Set the WEBHOOK_CALLBACK_URL in the relevant yaml file

      On Red Hat OpenShift:

      • Open overlays/openshift-all/deployment-patch.yaml.
      • Find WEBHOOK_CALLBACK_URL.
      • Edit the value - this should simply be a case of replacing {openshift_master_default_subdomain} with your actual value.

      On other Kubernetes environments:

      • Open overlays/plainkube-all/deployment-patch.yaml.
      • Find WEBHOOK_CALLBACK_URL.
      • Edit the value - this could simply be a case of replacing IPADDRESS with your actual value. If WEBHOOK_CALLBACK_URL protocol is https, ssl verification will be enabled on the github webhook and the TLS certificate secret set in WEBHOOK_TLS_CERTIFICATE is used in the ingress. If WEBHOOK_TLS_CERTIFICATE is not defined or the secret doesn't exit, the certificate signed by the platform certificate is created and used in the ingress. If the platform certificate is not issued by the certificate authority, the SSL verification option in the github webhook must be disabled manually. If the call back URL is not determined yet in Amazon EKS environment, replace IPADDRESS with a dummy address. It will be replaced in the step in the Getting Started guide.
    4. Apply the yaml

      On Red Hat OpenShift:

      kubectl apply -k overlays/openshift-latest

      On other Kubernetes environments:

      kubectl apply -k overlays/latest


You will be able to access the webhooks section of the dashboard once the pods are all up and running.

  • To monitor the pods:

    Run the kubectl get pods command to monitor the Tekton Dashboard Webhooks Extension component until all of the components show a STATUS of Running:

    kubectl get pods --namespace tekton-pipelines --watch

    Tip: Use CTRL + C to exit watch mode.



You are now ready to use the Tekton Dashboard Webhooks Extension - see our Getting Started guide.

Create webhook page in dashboard