[JIRA] (JENKINS-55760) IRC nick is configurable but does not map to Jenkins ID of sender in the "build" command

2 views
Skip to first unread message

jimklimov@gmail.com (JIRA)

unread,
Jan 24, 2019, 12:43:02 PM1/24/19
to jenkinsc...@googlegroups.com
Jim Klimov updated an issue
 
Jenkins / Bug JENKINS-55760
IRC nick is configurable but does not map to Jenkins ID of sender in the "build" command
Change By: Jim Klimov
Summary: IRC nick is configurable but does not map to Jenkins ID of sender in the "build" command
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jimklimov@gmail.com (JIRA)

unread,
Jan 24, 2019, 12:45:01 PM1/24/19
to jenkinsc...@googlegroups.com
Jim Klimov started work on Bug JENKINS-55760
 
Change By: Jim Klimov
Status: Open In Progress

jimklimov@gmail.com (JIRA)

unread,
Jan 24, 2019, 12:45:02 PM1/24/19
to jenkinsc...@googlegroups.com

jimklimov@gmail.com (JIRA)

unread,
Jan 24, 2019, 12:45:02 PM1/24/19
to jenkinsc...@googlegroups.com

jimklimov@gmail.com (JIRA)

unread,
Jan 24, 2019, 12:45:03 PM1/24/19
to jenkinsc...@googlegroups.com
Jim Klimov commented on Bug JENKINS-55760
 
Re: IRC nick is configurable but does not map to Jenkins ID of sender in the "build" command

https://github.com/jenkinsci/instant-messaging-plugin/pull/21 currently should address one part of this issue, allowing at least the "build" command for an account whose Jenkins name is same as IRC ID or nickname.

Matching the nickname to an optionally configured mapping (as exists for IRCbot plugin) proved tricky to implement in an arbitrary solution, so help would be welcome.

jimklimov@gmail.com (JIRA)

unread,
Jan 24, 2019, 12:52:02 PM1/24/19
to jenkinsc...@googlegroups.com

Note to self: seems the AbortCommand.java could benefit from similar security considerations, but does not check any such permissions at all, or I'm missing something...

jimklimov@gmail.com (JIRA)

unread,
Jan 24, 2019, 12:52:03 PM1/24/19
to jenkinsc...@googlegroups.com
Jim Klimov edited a comment on Bug JENKINS-55760
Note to self: seems the AbortCommand.java could benefit from similar security considerations, but does not check any such permissions at all (only declares the required permission) , or I'm missing something...

jimklimov@gmail.com (JIRA)

unread,
Aug 5, 2019, 11:06:02 PM8/5/19
to jenkinsc...@googlegroups.com
 

Fix merged, included in a new plugin release

Change By: Jim Klimov
Status: In Review Resolved
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages