Currently it is only possible to have a single job using the gitlab-branch-source-plugin for a repository due to the fact, that the context of the status updates is always 'jenkinsci/(branch|mr-head|mr-merge|tag)'.
      I see the reason in an ideal world, to have one job per project, but in real-life I stumbled to often over exactly that issue (previously on github projects).

      We have currently two use-cases for multiple jobs per repo.

      • First: Large project which has troubles with flaky UI-Tests. So UI-Tests are done in a separate Job to see clearly, that at least the build, code analysis, and the deployment works fine, regardless of the flakiness of the tests. So it would be great to have a 'jenkinsci/ui/branch' and a 'jenkinsci/build-and-deploy/branch' context.
      • Second: A project which consists of different modules in one repo, where every module has it's own multibranch-pipeline. Here a 'jenkinsci/server/branch' and a 'jenkinsci/client/branch' would be of use.

          [JENKINS-61020] Allow custom context for commit status

          A proposal is added as a PR: https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/75 I would be really happy about any feedback and maybe some hints for a proper name of the feature.

          Michael Musenbrock added a comment - A proposal is added as a PR:  https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/75 I would be really happy about any feedback and maybe some hints for a proper name of the feature.

          Kyle added a comment -

          Interested in this as well.  Provided an example of how I use it and how it worked for Bitbucket on the GitHub PR.

          Kyle added a comment - Interested in this as well.  Provided an example of how I use it and how it worked for Bitbucket on the GitHub PR .

          Thank you for this new improvement!

          Viacheslav Dubrovskyi added a comment - Thank you for this new improvement!

            baymac Parichay Barpanda
            redeamer Michael Musenbrock
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: