Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
None
-
Cloudbees Jenkins Enterprise 2.19.3.1, GitHub Enterprise
Description
- Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master in our case) is built. But a push to master does not trigger a build.
Attachments
Activity
Kyle Wayman
created issue -
Kyle Wayman
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description | Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master our case) is branched. But a push to master does not trigger a build. | * Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master our case) is built. But a push to master does not trigger a build. |
Kyle Wayman
made changes -
| Description | * Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master our case) is built. But a push to master does not trigger a build. | * Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master in our case) is built. But a push to master does not trigger a build. |
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
Probably fixed in the 2.0 series of GitHub Branch Source. Please re-open against GitHub Branch Source if not fixed there.
Closing this issue as with the 2.0 series of GitHub Branch Source the GitHub Organization Folders plugin is dead (functionality moved to GitHub Branch Source)