Bug 1362465 - Bugzilla bot account required
Summary: Bugzilla bot account required
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-02 09:24 UTC by Kaushal
Modified: 2016-08-22 03:31 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-22 03:31:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Kaushal 2016-08-02 09:24:04 UTC
Currently, review.gluster.org comments to bugzilla are done using Vijay's account (it was Avati's earlier). A bugzilla bot account needs to be used for this instead.

Comment 1 Niels de Vos 2016-08-02 12:21:15 UTC
Please use the bugs address (public mailinglist) for this.

Comment 2 Kaushal 2016-08-02 12:25:09 UTC
(In reply to Niels de Vos from comment #1)
> Please use the bugs address (public mailinglist) for this.

This doesn't seem a good idea to me. We can't be using a public mailing list for creating the bot account.
For the bot account my preference is to create a bugbot email (or an alias forwarding to the infra admins) and use it.

Comment 3 Nigel Babu 2016-08-02 12:39:10 UTC
I'm guessing we need two things here:

1) A bot account to change status and has bugzilla privileges to make changes.
2) An account that will forward bugs to a mailing list?

I'm going to exclusively focus on 1). That account will not send email publicly. It will make changes. Remember we need to grant this bug editbugs privileges, so I'll have to talk to bugzilla ops folks and take their suggestions on what works best.

Comment 4 Kaushal 2016-08-02 12:56:28 UTC
2 already works. You just need to set a default CC, which is already done.

Comment 5 Nigel Babu 2016-08-22 03:31:15 UTC
We now have bugzilla-bot which only has editbugs privileges which will do this from today.


Note You need to log in before you can comment on or make changes to this bug.