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

[jenkins-infra-bot]

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.

---

Originally reported by christian_rusin, imported from: Entering recommended refspec value for Gitlab job triggers an error

• status: Open
• priority: Blocker
• component(s): git-plugin, gitlab-plugin
• resolution: Unresolved
• votes: 0
• watchers: 5
• imported: 2025-12-02

Raw content of original issue

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

	
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.

1 attachment

• Screenshot 2024-07-29 at 14.39.24.png

  

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original 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.
  

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.

[jenkins-infra-bot]

christian_rusin:

• Original comment link
• Raw content of original comment:

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

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

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original 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.
  

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.