chekker

What it looks at:

What it looks with:

status: What is the status of a particular ups_database -- in other words, which versions of the products have been declared current (or any other chain), or which versions of the products are not chained at all? status is a reformatting of one or more ups_database files.

$ status  \
  [-group support-group]  \ # (default: *; special case for -group unknown)
  [-support dbfile]  \      # (default: $CHEKKER_DBSUPPORT)
  [-schedule dbfile]  \     # (default: $CHEKKER_DBSCHEDULE)
  [-notes notepath]  \      # (default: $CHEKKER_NOTEFILES/)
  [-chain value]  \         # (default: current; special case for -chain nochain)
  [-raw] \		    # (default: absent)
  [ups_database]            # (default: $CHEKKER_PRODUCTS)

schedule: What is the current development schedule for various products? schedule is a reformatting of the $CHEKKER_DBSCHEDULE file.

$ schedule  \
  [-group support-group]  \ # (default: *; special case for -group unknown)
  [-support dbfile]  \      # (default: $CHEKKER_DBSUPPORT)
  [-schedule dbfile]  \     # (default: $CHEKKER_DBSCHEDULE)
  [-notes notepath]         # (default: $CHEKKER_NOTEFILES/)

chekker: Are we meeting our published schedules? chekker is a correlation between the $CHEKKER_DBSCHEDULE and the versions/chains listed in the ups_database product declaration files.

$ chekker  \
  [-group support-group]  \ # (default: *; special case for -group unknown)
  [-support dbfile]  \      # (default: $CHEKKER_DBSUPPORT)
  [-schedule dbfile]  \     # (default: $CHEKKER_DBSCHEDULE)
  [-notes notepath]  \      # (default: $CHEKKER_NOTEFILES/)
  [ups_database]            # (default: $CHEKKER_PRODUCTS)

previous | up | next