[JIRA] (JENKINS-56602) Jenkins submitter input not working with , separated ID's

2 views
Skip to first unread message

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 18, 2019, 12:34:03 PM3/18/19
to jenkinsc...@googlegroups.com
saif rehman created an issue
 
Jenkins / Bug JENKINS-56602
Jenkins submitter input not working with , separated ID's
Issue Type: Bug Bug
Assignee: Alex Earl
Components: emailext-template-plugin
Created: 2019-03-18 16:33
Priority: Minor Minor
Reporter: saif rehman

Based on below Jenkins documentation description , I am using comma separated Id's to get email .It only works with one Id which is my employee Id for a project. If I add another employee Id separated by comma it doesn't work. below are the paramters

input message: "Do you want to approve this job to deploy to QA?", submitter: "897656,783425"

submitter (optional) : User IDs and/or external group names of person or people permitted to respond to the input, separated by ','. If you configure "alice, bob", will match with "alice" but not with "bob". You need to remove all the white spaces.

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

slide.o.mix@gmail.com (JIRA)

unread,
Mar 18, 2019, 4:30:02 PM3/18/19
to jenkinsc...@googlegroups.com
Alex Earl commented on Bug JENKINS-56602
 
Re: Jenkins submitter input not working with , separated ID's

Not sure why this was assigned to this component.

slide.o.mix@gmail.com (JIRA)

unread,
Mar 18, 2019, 4:30:02 PM3/18/19
to jenkinsc...@googlegroups.com
Alex Earl updated an issue
 
Change By: Alex Earl
Component/s: _unsorted
Component/s: emailext-template-plugin

slide.o.mix@gmail.com (JIRA)

unread,
Mar 18, 2019, 4:31:01 PM3/18/19
to jenkinsc...@googlegroups.com
Alex Earl assigned an issue to Unassigned
Change By: Alex Earl
Assignee: Alex Earl

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 18, 2019, 4:36:01 PM3/18/19
to jenkinsc...@googlegroups.com
saif rehman commented on Bug JENKINS-56602
 
Re: Jenkins submitter input not working with , separated ID's

I am not sure which component should be selected as part of this Bug so I just added above

slide.o.mix@gmail.com (JIRA)

unread,
Mar 18, 2019, 4:54:01 PM3/18/19
to jenkinsc...@googlegroups.com

Where are you putting this information (the id's). A screenshot might be helpful.

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 18, 2019, 5:31:02 PM3/18/19
to jenkinsc...@googlegroups.com
saif rehman updated an issue
 
Change By: saif rehman
Attachment: image-2019-03-18-16-30-34-914.png

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 18, 2019, 5:32:02 PM3/18/19
to jenkinsc...@googlegroups.com
saif rehman updated an issue
Change By: saif rehman
Attachment: image-2019-03-18-16-31-10-167.png

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 18, 2019, 5:34:02 PM3/18/19
to jenkinsc...@googlegroups.com
saif rehman updated an issue
Change By: saif rehman
Attachment: image-2019-03-18-16-33-39-705.png

slide.o.mix@gmail.com (JIRA)

unread,
Mar 18, 2019, 5:52:03 PM3/18/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins submitter input not working with , separated ID's

I'm not sure what you are expecting to happen here. 

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 19, 2019, 5:39:02 PM3/19/19
to jenkinsc...@googlegroups.com

Its sending me email with this input message but not to other users. My expectation is the email should be sent to all users whose ids are added inside the submitter

slide.o.mix@gmail.com (JIRA)

unread,
Mar 19, 2019, 6:13:01 PM3/19/19
to jenkinsc...@googlegroups.com

The input step has nothing to do with email, so I am not sure what you want to have happen.

vinothkumar.thirunavukkarasu@bcbsfl.com (JIRA)

unread,
Mar 20, 2019, 3:08:02 PM3/20/19
to jenkinsc...@googlegroups.com

Alex Earl : I have the same issue. When i input multiple jenkins user id for the input step as submitter (user1,user2), the expectation is either user1 or user2 can proceed with the input step. 

 
def approver = input (message: 'Deploy ?', ok: 'Approve', submitter: "user1,user2",submitterParameter: 'approver')
 
If you login to jenkins as user1 to proceed with approval, it errors out saying the current user is not part of user1,user2
 
 
 

vinothkumar.thirunavukkarasu@bcbsfl.com (JIRA)

unread,
Mar 20, 2019, 3:11:02 PM3/20/19
to jenkinsc...@googlegroups.com

Alex Earl There were instance i was able to get the issue reported when multiple ids passed as comma seperated. Currently i couldnt able to reproduce this issue again.

slide.o.mix@gmail.com (JIRA)

unread,
Mar 21, 2019, 9:22:02 AM3/21/19
to jenkinsc...@googlegroups.com

Vinoth Kumar Thirunavukkarasu The input step has nothing to do with emailext-template-plugin, that is what I am trying to figure out. I maintain that plugin, not anything to do with the input step.

vinothkumar.thirunavukkarasu@bcbsfl.com (JIRA)

unread,
Mar 21, 2019, 10:09:02 AM3/21/19
to jenkinsc...@googlegroups.com

Alex Earl I am with you that input step nothing to do with emailext  . The issue is specifically only to input step not working with multiple user ids with comma separated. Is there a way to tie up / tag the issue to the input step component ?

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 21, 2019, 11:01:02 AM3/21/19
to jenkinsc...@googlegroups.com

I second that, input step with comma separated for multiple ids not working. I tried using semi colon ; but same result.

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 21, 2019, 11:45:02 AM3/21/19
to jenkinsc...@googlegroups.com
saif rehman updated an issue
Change By: saif rehman
Attachment: image-2019-03-18-16-30-34-914.png

saif.rehman@cvshealth.com (JIRA)

unread,
Mar 21, 2019, 11:45:02 AM3/21/19
to jenkinsc...@googlegroups.com
saif rehman updated an issue
Change By: saif rehman
Attachment: image-2019-03-18-16-31-10-167.png

mark.earl.waite@gmail.com (JIRA)

unread,
Mar 7, 2020, 11:46:03 AM3/7/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
Change By: Mark Waite
Component/s: pipeline-input-step-plugin
Component/s: _unsorted
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages