jieryn added a comment - 2011-08-26 17:16 13:09:48 mwalling : jenkinsci_builds: help 13:09:48 jenkinsci : Available commands: 13:09:49 jenkinsci : abort <job> - specify which job to abort 13:09:49 jenkinsci : alias [<alias> [<command>]] - defines a new alias, deletes one or lists all existing aliases 13:09:50 jenkinsci : botsnack [<snack>] - om nom nom 13:09:50 jenkinsci : build <job> [now|<delay>[s|m|h]] [<parameterkey>=<value>]* - schedule a job build, with standard, custom or no quiet period 13:09:51 jenkinsci : cb - list jobs which are currently in progress 13:09:51 jenkinsci : comment <job> <build-#> <comment> - adds a description to a build 13:09:52 jenkinsci : currentlyBuilding - list jobs which are currently in progress 13:09:52 jenkinsci : h [<job>|-v <view>] - show the health of a specific job, jobs in a view or all jobs 13:09:53 jenkinsci : health [<job>|-v <view>] - show the health of a specific job, jobs in a view or all jobs 13:09:53 jenkinsci : jobs [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs 13:09:54 jenkinsci : q - show the state of the build queue 13:09:54 jenkinsci : queue - show the state of the build queue 13:09:55 jenkinsci : s [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs 13:09:55 jenkinsci : schedule <job> [now|<delay>[s|m|h]] [<parameterkey>=<value>]* - schedule a job build, with standard, custom or no quiet period 13:09:56 jenkinsci : status [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs 13:09:56 jenkinsci : testresult [<job>|-v <view>] - show the test results of a specific job, jobs in a view or all jobs 13:09:57 jenkinsci : userstat <username> - prints information about a Jenkins user 13:10:04 mwalling : "oops" 13:10:26 + jieryn : i think BlueMatt has a compelling argument

Mark Walling added a comment - 2011-08-26 17:16 < mwalling> although, i didn't think it talked in chanel < mwalling> jenkinsci_builds: help < jenkinsci_builds> Available commands: < jenkinsci_builds> abort <job> - specify which job to abort < jenkinsci_builds> alias [<alias> [<command>]] - defines a new alias, deletes one or lists all existing aliases < jenkinsci_builds> botsnack [<snack>] - om nom nom < jenkinsci_builds> build <job> [now|<delay>[s|m|h]] [<parameterkey>=<value>]* - schedule a job build, with standard, custom or no quiet period < mwalling> oh wow < jenkinsci_builds> cb - list jobs which are currently in progress < jenkinsci_builds> comment <job> <build-#> <comment> - adds a description to a build < jenkinsci_builds> currentlyBuilding - list jobs which are currently in progress < mwalling> sorry < jenkinsci_builds> h [<job>|-v <view>] - show the health of a specific job, jobs in a view or all jobs < jenkinsci_builds> health [<job>|-v <view>] - show the health of a specific job, jobs in a view or all jobs < jenkinsci_builds> jobs [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs < jenkinsci_builds> q - show the state of the build queue < jenkinsci_builds> queue - show the state of the build queue < jenkinsci_builds> s [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs < jenkinsci_builds> schedule <job> [now|<delay>[s|m|h]] [<parameterkey>=<value>]* - schedule a job build, with standard, custom or no quiet period < jenkinsci_builds> status [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs < jenkinsci_builds> testresult [<job>|-v <view>] - show the test results of a specific job, jobs in a view or all jobs < jenkinsci_builds> userstat <username> - prints information about a Jenkins user < mwalling> "oops" <+jieryn> i think BlueMatt has a compelling argument

kutzi added a comment - 2011-08-26 17:20 You can send a private message to the bot and it should answer to you via PM, too. IMO, it's quite consistent behaviour as it is: if you talk to the bot on the channel, you get the answer on the channel. If you talk via PM, you'll get the answer via PM.

Matt Corallo added a comment - 2011-08-26 17:30 Its nice in many cases, however in a public channel, people should not be allowed (or it should be configurable IMHO) to spam the channel by asking a bot for help.

Matt Corallo added a comment - 2011-08-26 17:35 <kutzi> BlueMatt, if you're concerned that the bot might spam a channel, IMO you shouldn't expose the bot in th 1st place <kutzi> IMO it can't be more simple than it is currently: PM cmd -> PM answer, chat cmd -> chat answer <BlueMatt> kutzi: I would like to do that, but if it wants to broadcast a single line for build fails, I think you have to, correct? <BlueMatt> or is there a way to not expose it and just pm the channel? <kutzi> I don't want to send the answer of cms a,b,d to channel and answers of c, e,f via pm <BlueMatt> in some channels, its much better to respond via pm, or not respond at all <kutzi> no, it's not possible <BlueMatt> for my specific case, Id love it to never respond to anything <kutzi> I'll think about that <BlueMatt> ok, well then I suppose I should have made the bug more clear... <kutzi> maybe an option to just inform is the way to go <BlueMatt> would work for me

kutzi added a comment - 2011-09-02 16:24 This is in a way related to JENKINS-5931 that both issues could be solved by supporting different types of chatrooms. E.g. privileged vs. non-privileged room resp. notifying vs. command-accepting room

kutzi added a comment - 2011-11-06 13:33 This has been fixed in a different way in JENKINS-11606 . If that's not sufficient for your use case please open a new bug with details.