-
Notifications
You must be signed in to change notification settings - Fork 461
Flags
David Kang edited this page Jun 11, 2020
·
2 revisions
- A
Flagis an on/off switch for something. Like- allow (
status=enable) publishing (flag=publish) for theArchitecturex86_64 (architecture_id=1) - do not (
status=disable) build (flag=build) for a specificRepository(repo=openSUSE_Tumbleweed) - allow (
status=enable) building (flag=build) for a specificRepository(repo=openSUSE_Tumbleweed) in theArchitecturex86_64 (architecture_id=1)
- allow (
- More specific
Flagsoverwrite unspecific flags. In the example above the thirdFlagoverwrites the second. -
Flagshave global defaults (FlagHelper::TYPES)
- A Project can have many
Flags - If a
Projectdoes not have aFlagfor a specific thing, the global default is taken.
- A
Packagecan have manyFlags - If a
Packagedoes not have aFlagfor a specific thing, theFlags of itsProjectare taken into account.
- 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