|
| 1 | +--- |
| 2 | +id: hyperexecute-github-app-integration |
| 3 | +title: GitHub Apps Integration Support for HyperExecute |
| 4 | +hide_title: false |
| 5 | +sidebar_label: GitHub App |
| 6 | +description: GitHub Apps Integration Support for HyperExecute |
| 7 | +keywords: |
| 8 | + - LambdaTest Hyperexecute |
| 9 | + - LambdaTest Hyperexecute help |
| 10 | + - LambdaTest Hyperexecute documentation |
| 11 | + - GitHub App |
| 12 | + - Integrations |
| 13 | + - Products |
| 14 | + - Automated testing alerts |
| 15 | + - DevOps communication |
| 16 | +url: https://www.lambdatest.com/support/docs/hyperexecute-github-app-integration/ |
| 17 | +site_name: LambdaTest |
| 18 | +slug: hyperexecute-github-app-integration/ |
| 19 | +--- |
| 20 | + |
| 21 | +import CodeBlock from '@theme/CodeBlock'; |
| 22 | +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; |
| 23 | + |
| 24 | +<script type="application/ld+json" |
| 25 | + dangerouslySetInnerHTML={{ __html: JSON.stringify({ |
| 26 | + "@context": "https://schema.org", |
| 27 | + "@type": "BreadcrumbList", |
| 28 | + "itemListElement": [{ |
| 29 | + "@type": "ListItem", |
| 30 | + "position": 1, |
| 31 | + "name": "Home", |
| 32 | + "item": "https://www.lambdatest.com" |
| 33 | + },{ |
| 34 | + "@type": "ListItem", |
| 35 | + "position": 2, |
| 36 | + "name": "Support", |
| 37 | + "item": "https://www.lambdatest.com/support/docs/" |
| 38 | + },{ |
| 39 | + "@type": "ListItem", |
| 40 | + "position": 3, |
| 41 | + "name": "Integration with Products", |
| 42 | + "item": "https://www.lambdatest.com/support/docs/hyperexecute-github-app-integration/" |
| 43 | + }] |
| 44 | + }) |
| 45 | + }} |
| 46 | +></script> |
| 47 | +HyperExecute supports integration with GitHub Apps, enabling secure, fine-grained, and scalable access to your GitHub repositories without relying on long-lived Personal Access Tokens (PATs). |
| 48 | + |
| 49 | +With this integration, HyperExecute automatically generates short-lived installation access tokens via GitHub Apps for all Git-related operations in Projects and Workflows, enhancing security, compliance, and maintainability. |
| 50 | + |
| 51 | +This integration supports three onboarding paths: |
| 52 | +- **LambdaTest's Marketplace GitHub App** (Public Cloud) |
| 53 | +- **Your Existing GitHub App** (On-Prem / Private Cloud) |
| 54 | +- **Private GitHub App Dedicated to Your Organization** (On-Prem / Air-Gapped) |
| 55 | + |
| 56 | +## How It Works |
| 57 | +1. Install a GitHub App using one of the three supported approaches. <br /> |
| 58 | +2. Complete the post-installation registration within the LambdaTest platform. <br /> |
| 59 | +3. HyperExecute backend (Logistics) sends data to Sentinel to persist details in the `github_app_integration` table. <br /> |
| 60 | +4. For customer-managed GitHub Apps, create an org-level secret using the Logistics Secrets API: `github_app_private_key_{{git_tenant}}`. <br /> |
| 61 | + |
| 62 | +Once setup is complete, all HyperExecute Project and Workflow Git operations use short-lived installation tokens instead of PAT tokens. The PAT-based flow is used only as a fallback when no GitHub App is configured. |
| 63 | + |
| 64 | +## Installation Approaches |
| 65 | +HyperExecute supports three installation models, depending on your cloud type and organizational setup. |
| 66 | + |
| 67 | +### Approach 1: LambdaTest's Marketplace GitHub App (Public Cloud) |
| 68 | + |
| 69 | +**Prerequisites :** |
| 70 | + |
| 71 | +- Admin permissions in your target GitHub organization |
| 72 | + |
| 73 | +**Installation Steps** |
| 74 | + |
| 75 | +1. Navigate to [GitHub Marketplace](https://github.com/marketplace) |
| 76 | +2. Search for "LambdaTest" or "HyperExecute" |
| 77 | +3. Open the LambdaTest GitHub App listing |
| 78 | +4. Click **Install** |
| 79 | +5. Select your target GitHub Organization |
| 80 | + - For GitHub Enterprise, installation must be completed per organization |
| 81 | +6. Configure repository access: |
| 82 | + - **All repositories** (recommended) |
| 83 | + - **Select repositories** |
| 84 | +7. Review the required permissions: |
| 85 | + - **Contents** (read/write) |
| 86 | + - **Metadata** (read) |
| 87 | +8. Click **Install** to complete the installation |
| 88 | + |
| 89 | +**Post-Installation Configuration** |
| 90 | + |
| 91 | +After installation, GitHub automatically redirects you to: `https://{{accounts_base_url}}/org-settings/hyperexecute/git-integration` |
| 92 | + |
| 93 | +The redirect URL includes an `installation_id` parameter required for configuration. |
| 94 | + |
| 95 | +> **Note:** Only Org Admins can complete the registration. Organization users can view mappings but cannot modify them. |
| 96 | +
|
| 97 | +### Approach 2: Your Existing GitHub App (On-Prem) |
| 98 | + |
| 99 | +**Prerequisites** |
| 100 | + |
| 101 | +- A GitHub App already exists in your GitHub organization |
| 102 | +- Admin access to the GitHub App |
| 103 | +- Required permissions are configured: |
| 104 | + - **Contents** (read) |
| 105 | + - **Metadata** (read) |
| 106 | + |
| 107 | +**Installation Steps** |
| 108 | + |
| 109 | +1. Obtain your app's installation ID from: |
| 110 | + - Navigate to **GitHub App → Installations → Installation URL** |
| 111 | + - Example URL format: `https://github.com/settings/installations/{installation_id}` |
| 112 | + |
| 113 | +2. Navigate to the LambdaTest setup page: |
| 114 | +``` |
| 115 | + https://{{accounts_base_url}}/org-settings/hyperexecute/git-integration |
| 116 | +``` |
| 117 | + |
| 118 | +3. Manually enter: |
| 119 | + - `installation_id` |
| 120 | + - Additional app details as required |
| 121 | + |
| 122 | +> **Note:** For GitHub Enterprise setups with multiple organizations, repeat this setup for each organization. |
| 123 | +
|
| 124 | +**Additional Required Configuration** |
| 125 | + |
| 126 | +Create an org-level secret via the Logistics Secret API: |
| 127 | +``` |
| 128 | +github_app_private_key_{{git_tenant}} |
| 129 | +``` |
| 130 | + |
| 131 | +This private key is used to generate short-lived tokens internally. |
| 132 | + |
| 133 | +### Approach 3: Private GitHub App (On-Prem Dedicated App) |
| 134 | + |
| 135 | +**Prerequisites** |
| 136 | + |
| 137 | +- Admin access in your target GitHub organization |
| 138 | +- Private GitHub App installation URL shared by the LambdaTest/Workflow team |
| 139 | +- Setup URL inside the GitHub App updated to the LambdaTest private setup URL |
| 140 | + |
| 141 | +**Installation Steps** |
| 142 | + |
| 143 | +1. Navigate to the private app installation URL: |
| 144 | +``` |
| 145 | + https://github.com/apps/{private-app-name}/installations/new |
| 146 | +``` |
| 147 | + |
| 148 | +2. Select your GitHub organization |
| 149 | + - Enterprise customers must repeat this process for each organization |
| 150 | + |
| 151 | +3. Configure repository access permissions |
| 152 | + |
| 153 | +4. Review and confirm the installation |
| 154 | + |
| 155 | +**Post-Installation Configuration** |
| 156 | + |
| 157 | +GitHub will redirect you to the private setup URL configured for your environment: |
| 158 | +``` |
| 159 | +https://{{private_accounts_base_url}}/org-settings/hyperexecute/git-integration |
| 160 | +``` |
| 161 | + |
| 162 | +The redirect contains the `installation_id` parameter, which is required for configuration. |
| 163 | + |
| 164 | +> **Note:** Only Org Admins can complete this configuration step. |
0 commit comments