Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73527

Entering recommended refspec value for Gitlab job triggers an error

      In the Jenkin's documentation for setting up a Freestyle job there is a recommendation:

      1. In the Advanced settings, set Name to origin and Refspec to +refs/heads/:refs/remotes/origin/ +refs/merge-requests//head:refs/remotes/origin/merge-requests/

      https://plugins.jenkins.io/gitlab-plugin/#plugin-content-git-configuration

      However setting up

      +refs/heads/:refs/remotes/origin/ +refs/merge-requests//head:refs/remotes/origin/merge-requests/

      into the dedicated field triggers the error (see the screen-shot attached).
      The format seem to respect the documentation.

          [JENKINS-73527] Entering recommended refspec value for Gitlab job triggers an error

          Mark Waite added a comment -

          Thanks for the report. I've confirmed that I see the same behavior when I paste the refspec from the documentation into a Freestyle project definition.

          Mark Waite added a comment - Thanks for the report. I've confirmed that I see the same behavior when I paste the refspec from the documentation into a Freestyle project definition.

          Christian added a comment -

          markewaite How fast do you think this can be corrected? Also do you think this bug is impacting the Gitlab-Jenkins connection?

          Christian added a comment - markewaite How fast do you think this can be corrected? Also do you think this bug is impacting the Gitlab-Jenkins connection?

          Mark Waite added a comment -

          christian_rusin I don't plan to work on this in the near future. My focus is on Spring Security 6.x Upgrade and changes related to that upgrade. Others are welcome to investigate further, explore if the warning message on the UI actually prevents anything from working, and share their findings with others. Pull requests are welcomed as are detailed investigations of the current behavior.

          Mark Waite added a comment - christian_rusin I don't plan to work on this in the near future. My focus is on Spring Security 6.x Upgrade and changes related to that upgrade. Others are welcome to investigate further, explore if the warning message on the UI actually prevents anything from working, and share their findings with others. Pull requests are welcomed as are detailed investigations of the current behavior.

            markewaite Mark Waite
            christian_rusin Christian
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: