I am testing a Jenkins CI/CD method. There is a single git repo with a Master branch, a QA branch, and a Dev branch. There are also many individual developer and feature branches that get merged into dev. The dev branch gets merged up to qa and qa up to master.
I have a jenkins environment using the gitlab-plugin where there is a folder containing a multibranch pipeline that runs the jenkinfiles in the developer/feature branches on any commit. It ignores the master, dev, and qa branches. In the folder is also 4 pipelines, 3 of which handle merge requests per each of the main branches. The fourth one is simply a deploy script for the master.
The issue is that GitLab's commit status for merge requests refuses to work when the multibranch pipeline is there. The CI tag just says can not connect to CI service after a merge request is submitted. However, if I remove the multibranch pipeline, the CI status tag immediately starts working.
Note that the builds are all still running fine in Jenkins, its simply gitlabs status tags that are the issue.
Any ideas on how to fix this?
edit: as I was reading this after submitting I realized how dumb it is to have 3 pipelines for merge requests, its only 1 now that handles all 3 branches
