-
Notifications
You must be signed in to change notification settings - Fork 441
The BackendPackage Cache
Henne Vogelsang edited this page Jul 31, 2023
·
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
Creates BackendPackage
if it does not exist for Package
if sources changed (Package.sources_changed
is called manually)
Refreshes (deletes/creates) BackendPackage
everytime the Backend changed the sources (New Event
for new revision, service run, undelete).
Creates BackendPackage
if it does not exist for all Package
s in Project
A job that is schedule if an IssueTracker
is saved:
- Creates
BackendPackage
if it does not exist for allPackage
that are links - Deletes
BackendPackage
of allPackage
s that are not links - Schedules an
UpdatePackagesIfDirtyJob
for allProject
s that containPackage
s withoutBackendPackage
- Development Environment Overview
- Development Environment Tips & Tricks
- Spec-Tips
- Code Style
- Rubocop
- Testing with VCR
- Authentication
- Authorization
- Autocomplete
- BS Requests
- Events
- ProjectLog
- Notifications
- Feature Toggles
- Build Results
- Attrib classes
- Flags
- The BackendPackage Cache
- Maintenance classes
- Cloud uploader
- Delayed Jobs
- Staging Workflow
- StatusHistory
- OBS API
- Owner Search
- Search
- Links
- Distributions
- Repository
- Data Migrations
- next_rails
- Ruby Update
- Rails Profiling
- Installing a local LDAP-server
- Remote Pairing Setup Guide
- Factory Dashboard
- osc
- Setup an OBS Development Environment on macOS
- Run OpenQA smoketest locally
- Responsive Guidelines
- Importing database dumps
- Problem Statement & Solution
- Kickoff New Stuff
- New Swagger API doc
- Documentation and Communication
- GitHub Actions
- How to Introduce Software Design Patterns
- Query Objects
- Services
- View Components
- RFC: Core Components
- RFC: Decorator Pattern
- RFC: Backend models