bob-status - Show SCM status
bob status [-h] [--develop | --release] [-c CONFIGFILE] [-D DEFINES] [--attic] [-r] [--sandbox | --no-sandbox] [--show-clean] [--show-overrides] [-v] [packages [packages ...]]
Show SCM status of existing workspaces.
This command is intended to list the status of all checkouts, especially
modifications, in a project. It can be used in two different modes. If the
command is invoked without a package then all workspaces of the project are
scanned for SCM changes. The other mode, when called with at least one
package, shows only the status of the given package(s). In this case the
--develop (default) and
--release options may be used to select the
-r scans the dependencies of the given package(s) too.
Consider attic directories too.
Normally SCMs that were moved to the attic next to the workspace are not checked. By using this option the attic directories that belong to a workspace are scanned too.
Bob versions before 0.15 did not store the locations of the attic directories in the project. If the project was initially built with an older version then the attic listing will probably be incomplete. In this case Bob will print a warning that you should not rely on the output.
Use additional user configuration file. May be given more than once.
The configuration files have the same syntax as
default.yaml. Their settings have higher precedence than
default.yaml, with the last given configuration file being the highest.
- Override default environment variable. May be given more than once. If the
VALUEis not supplied the variable will be defined to an empty string.
- Use developer mode. This is the default.
- Disable sandboxing
- Recursively display dependencies. Only direct dependencies are considered,
i.e. packages that are named in the
dependssection of the recipe. Consumed tool- and sandbox- packages that were forwarded are thus not visited.
- Use release mode.
- Enable sandboxing
- Show the status of a checkout even if unmodified. This includes
--show-overrides. See Verbosity below.
- Show checkouts that have active scmOverrides
O) even if the SCM is unchanged. Override information is always displayed if a checkout is shown but a
STATUSline is normally only emitted if the SCM was modified. Adding
-vwill additionally show the detailed override status. See Verbosity below.
- Increase verbosity. May be specified multiple times. See Verbosity below.
The output of bob status is one line per SCM checkout. Only existing workspaces are considered. A status line consists of one ore more status codes followed by the SCM path.
Status codes can be interpreted as follows:
?= missing information. The workspace was created by an older version of Bob that did not store enough information. The state of the SCM directory cannot be determined.
The directory can be in any state with respect to the original checkout. You should manually inspect it because it might contain unsaved changes.
A= attic. The recipe was changed for this checkout or the checkout is not referenced anymore in the recipe. The SCM path will be moved to the attic the next time the package is built.
C= collision. The SCM was not yet checked out but there is an existing file/directory at the checkout location. The next run of the checkout step will fail.
E= error. The SCM state could not be determined. The checkout is probably messed up. Use
-vto get additional information about the error.
M= modified. Some sources have been modified and not yet committed to SCM.
N= new. The SCM was not yet checked out. There might still be an old checkout at the same location. This is indicated by a simultaneous
Aflag (see above).
O= overridden. This SCM is affected by a scmOverrides. Pass
--show-overridesto force the output of a
STATUSline if the SCM is otherwise unmodified.
S= switched. The commit/tag/branch/URL is different from the recipe. In case of submodules the current commit is different from the one tracked in the parent tree.
U= unpushed commits on configured branch. Git only. Some commits were made locally to the configured branch but they have not yet been pushed to the remote.
u= unpushed commits not on configured branch. Git only. There are commits on other local branches than the configured branch, on a possibly detached HEAD or in the stash that have not been pushed to a remote. In case of shallowly cloned submodules this might be shown incorrectly because there is not enough information available about the remotes.
The command shows the status of the current checkout. If the recipe was changed and the next build would move a checkout to the attic then the current information still refers to the existing checkout.
By default modified checkouts (
U flags) and mismatches with
respect to the recipes (
S flags) are shown. Exceptional
conditions like a collision (
C flag), missing information to determine the
SCM status (
? flag) or if there was an error while retrieving the status
E flag) are always shown too.
By adding one or more
-v options the display of less important information
can be enabled. The following levels are available:
-vshows a detailed description of all important flags (
?). In particular the modified files and dirty commits of a SCM are listed. This level also shows git checkouts that have only unpushed commits that are not related to the configured branch (
uflag), but without detailed description.
-vvshows the full list of commits related to the
uflag. Additionally the status of SCMs that are not modified is shown, i.e. without flags or only the
Oflag. If you want to display this information without also enabling the detailed descriptions (see above) use
-vvvenables the detailed description of the
Oflag. Additionally skipped workspaces that do not exist are shown.