Send email notification to uploader if a package does not migrate

Bug #1645285 reported by Martin Pitt on 2016-11-28
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Auto Package Testing
Wishlist
Robert Bruce Park
britney
Wishlist
Robert Bruce Park

Bug Description

A lot of packages get stuck in -proposed for a long time due to introducing test regressions, FTBFS, causing uninstallability, or other policies. Britney should determine the uploader after it's clear that the package is permanently stuck and send an email notification.

Britney's policies have two different states REJECTED_TEMPORARILY and REJECTED_PERMANENTLY for that; for FTBFS it's pretty clear, but uninstallability might be temporary or permanent.

So this should mail the uploader and sponsor either as soon as britney knows that the excuse is invalid, or it has been in -proposed for > 2 days (to catch tests which are eternally in progress, for example).

A good first step would be to only notify because of Policy failures, and ignore ftbfs/uninstallability for now.

Martin Pitt (pitti) on 2016-11-28
Changed in britney:
status: New → Triaged
importance: Undecided → Wishlist
Steve Langasek (vorlon) on 2016-12-06
summary: - Send email notification to uploader if a package is invalid
+ Send email notification to uploader if a package does not migrate
Changed in britney:
assignee: nobody → Robert Bruce Park (robru)
Changed in auto-package-testing:
assignee: nobody → Robert Bruce Park (robru)
Martin Pitt (pitti) wrote :

- Launchpad API package uploader records have Person links for both the sponsor and the changelog uploader.
- Brian uses this/has code in the phased-updater notification which we should be able to reuse here.
- We also had this code in the old Jenkins-based autopkgtest system which still ought to live somewhere (contact point: jibel)

- snakefruit can send mail; for bileto the instance running britney should set up ssmtp or similar (autopkgtest infra does this in https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/tree/deployment/charms/xenial/autopkgtest-cloud-worker/hooks/config-changed#n32)

description: updated
Changed in auto-package-testing:
status: New → Triaged
importance: Undecided → Wishlist
Robert Bruce Park (robru) wrote :

Challenges:

1. Determine what email address to send mails to. lots of corner cases here; for bileto you want the name/email in debian/changelog, for syncs you want the syncer, not the debian uploader, for other cases you want the sponsor/signer. LP has this logic already, need to check if that's exposed through lplib anywhere. lplib getPackageSources returns a 'creator' field which corresponds to the sponsor, unlikely that this encapsulates the corner cases though.

2. Need to send emails (python probably has a few mail libraries, need to figure out which one supports precise through xenial with minimal hassle)

3. Need a system for caching who has been emailed about what, so that we don't spam people on every run.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers