Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/source/developing/workspaces.rst
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,8 @@ where build scripts automatically detect sources in it's configuration phase,
so newly added sources you add might be ignored.

In order to force the configuration step to be called again on the next build,
you can use :ref:`bst workspace reset --soft <invoking_workspace_reset>`, like so:
you can use :ref:`bst workspace reset <invoking_workspace_reset>` with the
``--soft`` option, like so:

In these cases, you can perform a hard reset on the workspace using
:ref:`bst workspace reset <invoking_workspace_reset>`, like so:
Expand Down Expand Up @@ -147,4 +148,3 @@ To discard the workspace completely we can do:

This will close the workspace and completely remove the workspace_hello
directory.

4 changes: 2 additions & 2 deletions src/buildstream/buildelement.py
Original file line number Diff line number Diff line change
Expand Up @@ -76,8 +76,8 @@

In the case that the element is currently workspaced, the ``configure-commands``
will only be run in subsequent builds until they succeed at least once, unless
:ref:`bst workspace reset --soft <invoking_workspace_reset>` is called on the
workspace to explicitly avoid an incremental build.
:ref:`bst workspace reset <invoking_workspace_reset>` is called with the
``--soft`` option on the workspace to explicitly avoid an incremental build.

"""

Expand Down