Hey everyone, inspired by @maralorn’s excellent bot, I’ve been working on a similar tool, that would allow me to subscribe to build failures of the nixpkgs-update tool.
You can find the bot at @nixpkgs-update-notify-bot:matrix.org (link), and the repo over here.
It periodicallyatm every 1hr fetches logs from https://github.com/nix-community/nixpkgs-update, notifying subscribers of any failure. It doesn’t have access to the builder’s exit code, so it has to resort to some dumb regex matching on the logs. I think if this proves to be useful, it could be cool to integrate it into the nixpkgs-update infrastructure, so it wouldn’t have to do that (and could develop other capabilities, e.g. a last_success command)
Please let me knowhere or by filing an issue if you encounter any problems.
UPDATE: The bot does not currently handle E2EE messaging (didn’t seem useful for such a bot), so if you send it encrypted messages it will not answer. This means the bot currently doesn’t work if you message it from Element X, whereas it does from Element.
UPDATE2: Current workaround is to add the bot to a public, unencrypted room.
i would love the option for per-maintainer rss feeds, or a static report of all packages whose most recent attempt was a failure, kinda like nix-review-tools does for hydra
This, or being able to subscribe to multiple packages in a single message, would be really nice. As it is, I’d have to send a lot of messages to subscribe to all the packages I maintain
Could you add a subscription to packages by regex?
My use case is that I want to be notified if one of vimPlugins.* will fail (I like to maintain them, but I don’t want to explicitly specify myself as a maintainer of 3000+ packages)
Some way of subscribing to multiple packages at once is definitely planned, but I’m not sure about the regex approach.
The main reason is that, exactly as you bring up, people could subsribe to thousands of packages (potentially all packages nixpkgs-update knows about, ~56000), which would put a lot of stress on the nix-community.org server.
There’s also the issue of accepting untrusted regexes, and I’d have to make sure there are not vulnerabilities there.
All in all, I’m much more likely to implement a hard-coded way of subscribing to e.g. the same package under multiple Python versions, than something like all vim plugins – sorry!