Ticket #55 (closed task: fixed)

Opened 7 years ago

Last modified 7 years ago

Find a way to detect package updates

Reported by: kparal Owned by: wwoods
Priority: major Milestone: Package Update Acceptance Test Plan
Component: watchers Keywords:
Cc: wwoods Blocked By:


Find out how to detect new package build (detect koji build? detect bodhi update?). It is important to know the process flow, how the packages travels from one system to another, and find a suitable place where the change can be detected and both old and new packages are accessible.

Change History

comment:1 Changed 7 years ago by jlaska

  • Cc wwoods added

Adding wwoods to the cc-list, I believe Will discussed this with Mike McLean? last week who provided some guidance.

Talked to mikem about watching koji builds - basically there is a
XML-RPC call (name??) that lists all recent builds (it has a builtAfter
argument or something like that, so you just do builtAfter=timestamp and
it shows you builds newer than that timestamp)

So, every couple of minutes:
- ask koji for a list of new builds
- add those builds to buildlist
- check each build in buildlist to see if it has been tagged
  # N.B. There is an interval between building and tagging so we *may*
need to check a new build more than once before it will actually have a
tag applied
  - if the build has a tag we're interested in
    - fire off tests for that nvr
      - an NVR is guaranteed to be unique in koji - one build, one NVR

comment:2 Changed 7 years ago by wwoods

  • Owner set to wwoods
  • Status changed from new to assigned

A prototype koji watcher has been checked into git:


we need to determine test requirements for post-koji-build tests in order to complete it.

comment:3 Changed 7 years ago by kparal

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

We are now detecting build updates, I think I can close this ticket.

Note: See TracTickets for help on using tickets.