-
Notifications
You must be signed in to change notification settings - Fork 461
BS Requests
An instance of BSRequest represents one request in OBS.
A request can have multiple actions (BsRequestAction). An action defines what will happen, when the request gets accepted. Every action is described in it's own sub-class for example if a request has a BsRequestAction of the type (string) submit, it will perform the code in BsRequestActionSubmit.
NOTE: The class BsRequestActionAcceptInfo is not an action itself. If a request was accepted, a new record of type BsRequestActionAcceptInfo is being created and it holds information about the accepted request.
Mappings:
| Type | Representative Class | Action |
|---|---|---|
| submit | BsRequestActionSubmit | changes source code or creates a new package |
| delete | BsRequestActionDelete | deletes a project/package |
| change_devel | BsRequestActionChangeDevel | changes the origin devel project of a project |
| add_role | BsRequestActionAddRole | adds a role (e.g. the submitter wants to be a project/package maintainer) |
| set_bugowner | BsRequestActionSetBugowner | sets the bugowner for a package |
| maintenance_incident | BsRequestActionMaintenanceIncident | usually comes from devel projects from the maintainer of a package in order to update a package in the distribution update channels. |
| maintenance_release | BsRequestActionMaintenanceRelease | a maintenance release request is created from a Maintenance Incident Project and is supposed to be released in the codestream and a set of products |
| group | BsRequestActionGroup | - no longer being used - |
This model holds always only one record in which it stores the number for the next request which will be created. When a new request gets created, the counter column gets increased by +1. This is required for HA setups which have multiple databases running where requests can have different ID's. To ensure that we always act on the right request, we use a unique number.
The BsRequestPermissionCheck model is being used for permission checks before a submit request can get accepted or a request state can be changed.
- 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