-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Anitya at release-monitoring.org #1058
Comments
BTW... wondering if anyone has/is already working on this? If not, I can look into contributing a PR assuming the maintainers here are willing to merge and deploy such a change? |
Hey! Anitya should be supported already. I can look into why you don't get notifications, what's your Fedora username? Thanks. |
My FAS ID is |
Ah, it looks like you don't have any rules at the moment. There aren't any default rules in the new FMN (that's issue #900), so you'll need to at least create a rule with the tracking rule named "My Events". It's at https://notifications.fedoraproject.org. |
Aha... I hadn't realised Anitya would be listed under "My Events". I think I'm a victim of poor UX. I've configured a rule so I'll see if that works out, thanks for the pointer. |
I have an Anitya rule under My Events enabled for months, but I never ever get a single message from it. The topic pattern is set to If this is true, is it possible to have a way to add a rule without a tracking rule or a special tracking rule for Anitya? |
Hey @lantw44 , if I understand correctly, I think this PR should help: fedora-infra/anitya-messages#70 |
@abompard Thank you. I got 2 messages from Anitya with the Artifacts tracking rule this week. |
My old FMN seem to have stopped working (getting a 503 error from that application) and the new FMN doesn't support Anitya. This is my main use case for FMN.
As a packager I would like to be notified about new releases of packages I maintain so that I can produce new package versions in a timely manner.
The text was updated successfully, but these errors were encountered: