-
Notifications
You must be signed in to change notification settings - Fork 461
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
- Refreshes BackendPackages of all Packages that are links
- Deletes BackendPackages of all Packages that are not links
- Schedules an UpdatePackagesIfDirtyJob for all Projects that contain Packages without BackendPackages
Creates a BackendPackage if the frontend changed the Package sources (Package.sources_changed is called manually)
Refreshes BackendPackage everytime the Backend changed the sources (new revision is created, service ran, undelete).
Creates a BackendPackage for all Packages that have none in Project
- Development Environment Overview
- Development Environment Tips & Tricks
- Spec-Tips
- Code Style
- Rubocop
- Testing with VCR
- Test in kanku
- 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
- Package Versions
- next_rails
- Ruby Update
- Rails Profiling
- 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
- Brakeman
- How to Introduce Software Design Patterns
- Query Objects
- Services
- View Components
- RFC: Core Components
- RFC: Decorator Pattern
- RFC: Backend models
- RFC: Hotwire Turbo Frames Pattern