Status: Closed (View Workflow)
Jenkins ver. 2.32.2, linux, latest plugin versions
We upgraded Jenkins to the latest version and plugins and migrated from the github-organization-folder plugin to the GitHub Branch Source plugin as described here:
Before the migration we had the following architecture and functions:
We connected a github enterprise with jenkins. We used the github and github-organization-folder plugins and configured folders with specific pattern that match to the github repositories. Jenkins created jobs for repo+branch. In Github we configured one global organization hook that notify jenkins about branch updates, pushes and pull requests. As result jenkins automatically reflected changes in Github in jenkins:
- Trigger a build job after a Git Commit/push
- Create a new job configuration for a new branch
- Delete a existing job configuration when a branch was deleted
After the migration and followed the upgrade strategy the described functions completely stopped. It is a blocking issue.
The blog entry described that "The functionality of this plugin [GitHub Organization Folders Plugin] has been migrated to the GitHub Branch Source plugin". We did not find any information that these usecases are deprecated and assume that they are still valid usecases.
How can we active the functions again? Please can you provide instructions how to enable again or fix the issue.
JENKINS-37845 GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
I suspect that your hooks are misconfigured somehow. This all works just fine for me and quite a number of other users.
JENKINS-37845 as that issue is about providing better diagnostics on hooks being incorrectly configured
The hooks worked before and we did not change anything except updating the Jenkins with the plugins. After this it stop to work.
Can you explain how you think it is misconfigured when it worked before?
Do you have an outlook for providing better diagnostics and documentation to the configuration of the hook that we can use to verify the setup?
Maybe I have to mention that we have GitHub Enterprise and we have a a global hook for the Git Org. I am not sure if this is similar to the quite number of other users.
I agree that are no diagnostic information to debug the issue except. Which plugin should handle the hook event?
Are there any news?