#9778 Reduce the number of repos in pagure that fm-releng notifies in #fedora-releng channel
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by mohanboddu.

  • Describe the issue

Currently when someone writes in pagure including the keywords like compose, pungi and others in any repo, it will send a notification on #fedora-releng freenode channel, lets reduce the number of repos and only track certain releng related repos.

This is annoying some users as its sending a notification to them.

This needs fixing to the regex in https://pagure.io/fedora-infra/ansible/blob/master/f/roles/fedmsg/irc/templates/ircbot.py#_221

  • When do you need this? (YYYY/MM/DD)

Whenever possible.


Yes, please! :confetti_ball:

Metadata Update from @mohanboddu:
- Issue tagged with: low-gain, low-trouble, ops

3 years ago

certain releng related repos.

So which are those?

This repo, then?

I'm not sure what exactly @mohanboddu meant, but I think the idea is that the IRC bot wouldn't react on a "compose" and similar words mentioned in ANY Pagure ticket, but only in tickets from releng-related repos (enumerated or matched with some wildcard).

After being constantly pinged by fm-releng about a half of the actions I do in Pagure, I decided to leave the #fedora-releng IRC channel until this is resolved. It is very annoying.

<fm-releng> pagure.issue.comment.added -- kparal commented on ticket fedora-qa#622: "Link/merge IoT release criteria from/into QA release criteria" https://pagure.io/fedora-qa/issue/622#comment-708458
<fm-releng> pagure.issue.new -- kparal opened a new ticket fedora-qa#659: "Make rpm-ostree testcases generic - usable for IoT, Silverblue and CoreOS" https://pagure.io/fedora-qa/issue/659
<fm-releng> pagure.issue.assigned.added -- kparal assigned ticket fedora-qa#659 to sumantrom https://pagure.io/fedora-qa/issue/659
<fm-releng> pagure.issue.comment.added -- kparal commented on ticket fedora-qa#659: "Make rpm-ostree testcases generic - usable for IoT, Silverblue and CoreOS" https://pagure.io/fedora-qa/issue/659#comment-708461
<fm-releng> pagure.issue.edit -- kparal edited the close_status and status fields of ticket fedora-qa#635 https://pagure.io/fedora-qa/issue/635
<fm-releng> pagure.issue.comment.added -- kparal commented on ticket fedora-qa#635: "Make sure we have some rpm-ostree coverage in OpenQA" https://pagure.io/fedora-qa/issue/635#comment-708464

So, the problem here is that we don't have a lot to work with. We can match fedmsgs on topic or body, but with a weird syntax. ;(

In https://pagure.io/fedora-infra/ansible/c/70d84a4686878145b24c9e0584b6fa7411beddc5?branch=master I attempt to restrict it to only relengy things...

@kparal can you try a commit that would get it notifying and see if it's any better now?

I commented in those two tickets mentioned above (and then removed those comments), and I didn't get pinged on #fedora-releng. So this is a massive improvement, thanks a lot!

I think the problem was that they contained the word "compose" and you used to match any ticket with a "compose" in its text.

I'll monitor the situation and I'll update this ticket if I still see some invalid matches (outside of releng-y stuff). But it looks good now.

ok, great. Please re-open if we need to adjust more.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Done