-
Bug
-
Resolution: Duplicate
-
Blocker
-
None
-
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:
https://jenkins.io/blog/2017/01/17/scm-api-2/.
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.
Thanks.
- duplicates
-
JENKINS-37845 GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
- Resolved