Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: gitlab-branch-source-plugin
-
Labels:None
-
Similar Issues:
Description
Currently project name strategy set job name witch can be not safe to do because of symbols used in GitLab project name. Not all build tools correctly handle spaces and/or non ASCII symbols.
It would be nice to set job display name instead witch is safe and convenient.
Attachments
Activity
Sorry for confusing - I told about project naming strategy. If Giglab project name does not contains ASCII characters jobs is NOT created for that project. That looks like the bug.
It wold be best to set job name according to default strategy but job display name to GitLab project name.
Vladimir Konkov
added a comment - Sorry for confusing - I told about project naming strategy. If Giglab project name does not contains ASCII characters jobs is NOT created for that project. That looks like the bug.
It wold be best to set job name according to default strategy but job display name to GitLab project name. Joseph Petersen (old) If you are free, can you take a look at this issue?
Vladimir Konkov I think we tried to do what you are suggesting but it was not possible to implement at that time due to underlying architecture (I mean the SCM Plugin on which our plugin depends heavily). But Joseph Petersen (old) is best placed to answer you issue as he implemented this feature.
Hi Vladimir Konkov, first of all I would like to make an apology for late reply. I want to know if you are talking about the default project naming strategy or the project naming strategy trait?