-
Notifications
You must be signed in to change notification settings - Fork 441
SCM integration workflows.yml format
Victor Pereira edited this page Jun 3, 2021
·
3 revisions
File should be named workflows.yml
. Other variations like workflows.yaml
aren't supported
For now we are supporting the following schema:
workflow: # the name of the workflow. A regular string
steps: # list of steps
- branch_package: # the name of the step. It is defined by the OBS. Today just branch_package is supported
source_project: home:Admin # OBS source project
source_package: hello_world # OBS package to be branched
- 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