Release Infrastructure/BOSS/Standard workflow

Revision as of 22:19, 30 April 2011

BOSS comes with a sample "standard workflow" which consists of:

• a plugin to the OBS to intercept the event notifications
• the robogrator process launcher
• a coherent set of participants

This is not a mandatory workflow but was developed at Nokia and is designed to be useful for MeeGo vendors

Installation and source

Package : https://build.pub.meego.com/package/show?package=boss-launcher-robogrator&project=Project:MINT:Testing

GIT : https://meego.gitorious.org/meego-infrastructure-tools/boss-launcher-robogrator NOTE: skynet branch for now

Robogrator Process Launcer

Robogrator is the robotic package integrator. It reacts to the events occuring on the OBS and looks at the data inside to identify which project-specific process to launch.

It uses the data sent by the obs-boss-plugin to create a fresh process.

All processes have the fields:

• project : the project used to drive the process. Usually the project the package is in but for requests type events this is the target project.
• ev : the (undocumented) OBS Notify object parameters

For the actual process, robogrator uses the namespace/project/event-label to find a specific ruote process.

For the standard workflow the first participant is the standard_workflow_handler

It is configured in /etc/skynet/robogrator.conf

standard_workflow_handler

This participant serves two purposes:

• tracks packages that are rebuilt when a repo is published
• set some standard fields used by other participants

• REPO_PUBLISHED
  • repository
  • packages (packages successfully built in this build/publish cycle)
• BUILD_UNCHANGED, BUILD_SUCCESS, BUILD_FAIL
  • package
• SRCSRV_CREATE_PACKAGE, SRCSRV_DELETE_PACKAGE
  • package
• SRCSRV_VERSION_CHANGE
  • package
  • rev
  • version
• SRCSRV_REQUEST_*
  • actions
  • who
  • rid
  • description
  • when