Ticket #151 (closed task: fixed)

Opened 7 years ago

Last modified 7 years ago

RFE: opt-in email from autoqa's post-koji-build tests

Reported by: skvidal Owned by:
Priority: minor Milestone:
Component: resultdb Keywords:
Cc: Blocked By:

Description (last modified by jlaska) (diff)

Right now all koji builds are being tested with rpmguard and rpmlint on the backend.

The output is going to: https://fedorahosted.org/mailman/listinfo/autoqa-results

It'd be great if there were a way for a maintainer to opt-in to this kind of info for their package.

Not sure where the info would be stored - but the results from each build, instead of emailing to autoqa-results would send that to $srpmname-owner@…

and then anyone who is on that email alias gets the notices.

so what we need is:

  1. a place to say which packages have opted in
  2. maybe a partial solution to ticket#148
  3. that sounds like it.

Change History

comment:1 Changed 7 years ago by jlaska

  • Description modified (diff)

Thanks for the ticket Seth! Please ignore this comment, minor change so TRAC formats as intended.

comment:2 Changed 7 years ago by skvidal

location on fedorapeople is available

code to check a path there

import urllib import socket

def package_optin(name,release):

"""take a package name and release and check for an autoqa-optin file""" url = 'http://fedorapeople.org/packages/' fullurl = url + '%s/%s/%s/autoqa-optin' % (name[0], name, release) tmout = socket.getdefaulttimeout() socket.setdefaulttimeout(5) # if it takes more than try:

h = urllib.urlopen(fullurl)

except IOError, e:

socket.setdefaulttimeout(tmout) return False

socket.setdefaulttimeout(tmout) if h.getcode() == 200:

return True

return False

comment:3 Changed 7 years ago by kparal

Hello Seth, there are some changes in progress that could simplify things. We are working on ResultsDB:


where we want to store all the results. They won't be sent to mailing list afterwards. After each result is stored in ResultsDB, a notification will be sent to Fedora Message Bus. From the message bus different tools (Bodhi, Koji, PackageDB, etc) can pick up interesting messages and do something with it.

I suppose tools like Koji/Bodhi? can then inform maintainers about test results. Or we can create very simple tool intercepting messages on the bus and just providing some email and web syndication feeds to interested parties.

comment:4 Changed 7 years ago by skvidal

I know about resultsdb - I guess I'm not sure how likely that is to happen 'right away' and wwoods asked me to file this ticket and see what I could do to make it happen sooner.

comment:5 Changed 7 years ago by kparal

Oh I see. ResultDB won't be 'right away' I guess :) So some temporary solution makes sense if desired.

Just a question - those $srpmname-owner@… aliases already exist for every available package?

In that case it shouldn't be hard to tweak AutoQA a bit and send those emails.

I guess we would just then announce availability of that service and anyone who would like to be emailed would create a ticket for it here. We would then modify the list on fedorapeople.org.

comment:6 Changed 7 years ago by skvidal

the aliases already exist, yes.

And I would not recommend us modifying the list on fedorapeople.org - we just tell folks the service exists and if they want to get the notices then they can touch the files on fedorapeople.org - the dir is owned by the packager group - so anyone who is a packager can do that.

comment:7 Changed 7 years ago by skvidal

Here's what the instructions look like, I think:

you wanna get info on broken stuff (if anything) in your just-built-in-koji packages?

Info like: https://fedorahosted.org/pipermail/autoqa-results/2010-April/013903.html and https://fedorahosted.org/pipermail/autoqa-results/2010-April/013904.html

Then all you have to do is:

  1. ssh fedorapeople.org
  2. cd /srv/people/site/packages/
  3. cd $first-letter-in-lower-case-of-the-name-of-your-package
  4. mkdir $yourpackagename
  5. cd $yourpackagename
  6. mkdir $release (ex: F-13, devel, F-12, EL-5)
  7. touch $release/autoqa-optin

that's it!

comment:8 Changed 7 years ago by skvidal

one minor change to the test code.

make name[0] be name[0].lower()

comment:9 Changed 7 years ago by skvidal

patch sent to autoqa-devel

comment:10 Changed 7 years ago by kparal

  • Status changed from new to closed
  • Resolution set to fixed

Pushed into master. Thanks, Seth!

comment:11 Changed 7 years ago by skvidal

thankyou, kamil

Note: See TracTickets for help on using tickets.