Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Configuring Tekton webhooks in GitLab and Bitbucket

Red Hat Trusted Application Pipeline 1.5

Learn how to add webhooks to your source code repository when you select Tekton as a CI provider.

Red Hat Trusted Application Pipeline Documentation Team

Abstract

This document provides instructions on adding webhooks to your source code repository when you select Tekton as a CI provider.

Preface

When you select Tekton as your CI provider while creating an application, you must add webhooks to your source code repository, for example, GitLab or Bitbucket. These webhooks automatically trigger pipeline runs in RHDH when code is updated. This integration ensures that your pipeline is always in sync with your code changes.

Chapter 1. Configuring GitLab Webhooks to enable automated pipeline triggers

Set up webhooks in GitLab to automatically trigger pipeline runs in RHDH upon code updates.

Prerequisites

  • You must have integrated GitLab during the RHTAP install process.

  • You have a source repository. To locate your application’s source code:

    1. On the RHDH platform, navigate to the Catalog, select an appropriate application where GitLab is configured as the repository host.
    2. Go to the Overview tab and select View Source to open the repository where your application’s source code is housed.
  • You have a Webhook URL and a Secret Token. You can find these credentials in your private.env file.

Procedure

  1. Navigate to your GitLab source repository.

    1. On the Red Hat Developer Hub platform, navigate to the Catalog, select an application where GitLab is configured as the repository host.
    2. Go to the Overview tab and select View Source to open the repository for your source code.
  2. Go to Settings > Webhooks.
  3. In the URL field, enter the webhook URL.
  4. In the Secret Token field, enter the secret token.

  5. In the Trigger section:

    1. Select Push events.
    2. Select Merge request events.
  6. Click Add Webhook.

Verification

  1. Commit any change to the source repository in GitLab.
  2. Navigate to the CI tab in RHDH.
  3. Verify that a pipeline run is triggered for your code push.

Chapter 2. Configuring Bitbucket webhooks to enable automated pipeline triggers

Set up webhooks in Bitbucket to automatically trigger pipeline runs in RHDH upon code updates.

Prerequisites

  • You must have integrated Bitbucket during the RHTAP install process.

  • You have a source repository. To locate your application’s source code:

    1. On the RHDH platform, navigate to the Catalog, select an appropriate application where Bitbucket is configured as the repository host.
    2. Go to the Overview tab and select View Source to open the repository where your application’s source code is housed.
  • You must have a Webhook URL. You can find these credentials in your private.env file.

Procedure

  1. Navigate to your Bitbucket source repository.
  2. Go to Repository settings > Webhooks, and select Add webhook.
  3. In the Title field, enter an appropriate title.
  4. In the URL field, enter the webhook URL.

  5. . In the Trigger section:

    1. Select Push.
    2. Select Merged.
  6. Select Save.

Verification

  1. Make a code change in your Bitbucket repository and push the changes.
  2. Navigate to the CI tab in RHDH.
  3. Verify that a pipeline run is triggered after your code update.





Revised on 2025-04-30 03:56:12 UTC

Legal Notice

Copyright © 2025 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat, Inc.