Skip to content

BinaryRelease

Henne Vogelsang edited this page Jun 21, 2024 · 1 revision

The BinaryRelease table is basically a "log" of the "binaries" (RPM packages, ISO images, disk images etc.) the OBS created for a Repository. This is not done by default and needs to be enabled in the per project in the backend configuration ($BSConfig::packtrack).

Workflow

  • During publishing the backend stores the binaries it sees and notifies the frontend
  • an Event::Packtrack gets stored in the database
  • a UpdateReleasedBinariesJob get's scheduled by the Event creation
  • the UpdateReleasedBinariesJob:
    • asks the backend for the binaries it has seen for this event
    • replaces Repository.binary_releases with the set of binaries it got from the backend
    • BinaryRelease that are not in the set anymore are marked as obsolete
    • BinaryRelease that are not new but just "altered" are marked as modified
  • People can search them via https://api.opensuse.org/apidocs/#/Search/get_search_released_binary
Clone this wiki locally