Skip to content

The BackendPackage Cache

Henne Vogelsang edited this page Aug 10, 2017 · 11 revisions

Each Package has one BackendPackage which serves as cache for additional backend Package data (srcmd5, verifymd5 etc.). For invalidating/refreshing this cache there are several jobs

UpdatePackageMetaJob

If an IssueTracker is saved:

  • Creates BackendPackage if it does not exist for all Package that are links
  • Deletes BackendPackage of all Package that are not links
  • Schedules an UpdatePackagesIfDirtyJob for all Projects that contain Packages without BackendPackages

PackageUpdateIfDirtyJob(package)

Creates BackendPackage if it does not exist for Package if sources changed (Package.sources_changed is called manually)

UpdateBackendInfosJob(package)

Refreshes (deletes/creates) BackendPackage everytime the Backend changed the sources (New Event for new revision, service run, undelete).

UpdatePackagesIfDirtyJob(project)

Creates BackendPackage if it does not exist for all Packages in Project

Clone this wiki locally