Blockerbugs CLI

Synopsis

blockerbugs command [options]

Possible Commands

init_db, add_milestone, add_release, generate_config, sync-updates, sync-bugs, sync, upgrade_db

Description

The blockerbugs CLI is an interface for configuring and controlling the blocker tracking app.

Commands

init_db

Initialize the database using the global configuration

add_milestone

Adds a milestone to the tracker. Required options: -r -m -b -a

add_release

Adds a Fedora release to the tracker. Required options: -r

generate_config

Generates a template config file with a SECRET_KEY. Optional options: -d, -z

sync

Uses the applications config settings and stored information about milestones and releases to sync information about blocker/FE bugs for currently active milestones and bodhi updates which are marked as fixing those bugs

sync-updates

Runs sync but does not sync bug information from bugzilla, only updates from bodhi.

sync-bugs

Runs sync but does not sync with bodhi, only pulls information from bugzilla

upgrade_db

Upgrades the currently configured database to the alembic head - requires a database user with privelages to change the schema.

Options

-f, –full

Forces a full sync of bugs and updates instead of just the bugs which have changed since last sync. Default: False

-c, –check

Force check for missing bugs after sync operation

-d, –dburi

URI of database to use during config file generation

-r ,–release

The release number to use for milestone and release creation.

-m –milestone

The milestone name to use for milestone creation

-b, –blocker

The blocker tracking bugid for a milestone

-a, –accepted

The FE tracking bugid for a milestone

-z, –bzcookie

Location of bugzilla cookie to use. This should not be used outside of development environments as it causes problems when used with a non-regular user account.