[JIRA] (JENKINS-58445) Decide on GitLab Pipeline status notifier strategy

12 views
Skip to first unread message

parichay.barpanda@gmail.com (JIRA)

unread,
Jul 11, 2019, 10:46:02 AM7/11/19
to jenkinsc...@googlegroups.com
Parichay Barpanda created an issue
 
Jenkins / Improvement JENKINS-58445
Decide on GitLab Pipeline status notifier strategy
Issue Type: Improvement Improvement
Assignee: Parichay Barpanda
Components: gitlab-branch-source-plugin
Created: 2019-07-11 14:45
Labels: gsoc-2019
Priority: Minor Minor
Reporter: Parichay Barpanda

See https://github.com/baymac/gitlab-branch-source-plugin/pull/22#issuecomment-510342809
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

justin@harringa.com (JIRA)

unread,
Jul 17, 2019, 9:51:02 AM7/17/19
to jenkinsc...@googlegroups.com
Justin Harringa commented on Improvement JENKINS-58445
 
Re: Decide on GitLab Pipeline status notifier strategy

Perhaps this story should be the simpler thing to implement and then another story could be to add the other option? I suspect that just the overall pipeline status would be easier but Parichay Barpanda can make that determination.

justin@harringa.com (JIRA)

unread,
Jul 17, 2019, 9:52:02 AM7/17/19
to jenkinsc...@googlegroups.com
Justin Harringa edited a comment on Improvement JENKINS-58445
RE: comment about potentially allowing the user to provide the option of how they'd like statuses to show up in GitLab - 

 Perhaps this story should be the simpler thing to implement and then another story could be to add the other option? I suspect that just the overall pipeline status would be easier but [~baymac] can make that determination. :)

justin@harringa.com (JIRA)

unread,
Jul 17, 2019, 9:53:02 AM7/17/19
to jenkinsc...@googlegroups.com
Justin Harringa edited a comment on Improvement JENKINS-58445
RE: comment about potentially allowing the user to provide the option of how they'd like statuses to show up in GitLab - 

Perhaps this story should be the simpler thing to implement and then another story could be to add the other option? I suspect that just the overall pipeline status would be easier but [~baymac] can make that determination. :)  Thoughts [~jequals5]?

marky.r.jackson@gmail.com (JIRA)

unread,
Jul 17, 2019, 9:55:01 AM7/17/19
to jenkinsc...@googlegroups.com

I agree. Overall pipeline status is much easier but will also leave that up to Parichay Barpanda

parichay.barpanda@gmail.com (JIRA)

unread,
Jul 17, 2019, 10:01:02 AM7/17/19
to jenkinsc...@googlegroups.com

Thanks Justin Harringa and Marky Jackson I will implement this feature.

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 30, 2019, 3:29:30 AM7/30/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
 
Change By: Oleg Nenashev
Sprint: GSoC 2019. Coding Phase 2 , GSoC 2019. Coding Phase 3

szuberskidamian@gmail.com (JIRA)

unread,
Mar 9, 2020, 7:00:07 AM3/9/20
to jenkinsc...@googlegroups.com
Damian Szuberski commented on Improvement JENKINS-58445
 
Re: Decide on GitLab Pipeline status notifier strategy

Hello!

Currently gitlab-branch-source-plugin registers whole pipeline as one stage in Gitlab which is horrible for visibility. Would it be possible to incorporate here gitlabCommitStatus() clause from https://github.com/jenkinsci/gitlab-plugin so users can tune the granularity on their own?
Alternatively, is it somehow possible to provide such behavior automagically?
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages