[JIRA] (JENKINS-59581) Set job display name from GitLab project name

8 views
Skip to first unread message

vkonkov@citc.ru (JIRA)

unread,
Sep 30, 2019, 4:51:02 AM9/30/19
to jenkinsc...@googlegroups.com
Vladimir Konkov created an issue
 
Jenkins / Improvement JENKINS-59581
Set job display name from GitLab project name
Issue Type: Improvement Improvement
Assignee: Parichay Barpanda
Components: gitlab-branch-source-plugin
Created: 2019-09-30 08:50
Priority: Major Major
Reporter: Vladimir Konkov

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.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

parichay.barpanda@gmail.com (JIRA)

unread,
Oct 2, 2019, 2:33:03 AM10/2/19
to jenkinsc...@googlegroups.com
Parichay Barpanda commented on Improvement JENKINS-59581
 
Re: Set job display name from GitLab project name

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?

vkonkov@citc.ru (JIRA)

unread,
Oct 6, 2019, 5:44:04 AM10/6/19
to jenkinsc...@googlegroups.com

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.

parichay.barpanda@gmail.com (JIRA)

unread,
Oct 7, 2019, 7:12:02 AM10/7/19
to jenkinsc...@googlegroups.com

Joseph Petersen If you are free, can you take a look at this issue?

parichay.barpanda@gmail.com (JIRA)

unread,
Oct 7, 2019, 7:16:01 AM10/7/19
to jenkinsc...@googlegroups.com

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 is best placed to answer you issue as he implemented this feature.

Reply all
Reply to author
Forward
0 new messages