Skip to content

Commit

Permalink
Merge pull request #769 from buildtesters/update_docs
Browse files Browse the repository at this point in the history
Update Documentation
  • Loading branch information
shahzebsiddiqui authored Jun 11, 2021
2 parents 6b05545 + 84726d2 commit 006b43e
Show file tree
Hide file tree
Showing 18 changed files with 899 additions and 848 deletions.
1 change: 1 addition & 0 deletions buildtest/cli/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -352,6 +352,7 @@ def config_menu(subparsers):
subparsers_compiler_find = compilers.add_subparsers(
description="Find new compilers and add them to detected compiler section",
dest="compilers",
metavar="",
)

compiler_find = subparsers_compiler_find.add_parser(
Expand Down
2 changes: 0 additions & 2 deletions buildtest/cli/history.py
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,6 @@ def list_builds():
# only filter filters that are 'build.json'
history_files = [f for f in history_files if os.path.basename(f) == "build.json"]

print(sorted(history_files))

table = {
"id": [],
"hostname": [],
Expand Down
3 changes: 2 additions & 1 deletion buildtest/schemas/definitions.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,8 @@
"enum": [
"lsf",
"slurm",
"cobalt"
"cobalt",
"pbs"
]
},
"user": {
Expand Down
6 changes: 3 additions & 3 deletions buildtest/settings/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,9 @@ system:
compiler:
gcc:
builtin_gcc:
cc: /usr/bin/gcc
fc: /usr/bin/gfortran
cxx: /usr/bin/g++
cc: gcc
fc: gfortran
cxx: g++

# location of log directory
# logdir: /tmp/
Expand Down
11 changes: 4 additions & 7 deletions docs/builder.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,6 @@
Build and Test Process
======================

Pipeline
---------

The `buildtest build` command is responsible for building and running tests. Every buildspec
goes through a pipeline that discovers buildspecs, validates the buildspec and builds and runs
the test. The buildspec must go through each stage of the pipeline, if it fails in one of the stage,
Expand All @@ -14,7 +11,7 @@ the buildspec will be ignored.
.. image:: _static/GeneralPipeline.png

Discover Buildspecs
~~~~~~~~~~~~~~~~~~~~
---------------------

buildtest will discover buildspecs based on command line arguments since you can
build by file, directory, executor, or tags. In **discover** stage, buildtest
Expand All @@ -28,7 +25,7 @@ and one of the sub-schemas, check :ref:`parsing buildspecs <parse_stage>` sectio
.. _parse_stage:

Parse Buildspecs
~~~~~~~~~~~~~~~~~
---------------------

A buildspec file may contain one or more test sections specified via ``buildspec``
field. Each test is validated by a sub-schema specified by ``type`` field.
Expand All @@ -43,7 +40,7 @@ Buildspecs will be ignored if it fails validation process for instance you may h
Invalid buildspecs won't be sent to **build** stage since we can't reliably build a test-script.

Building Buildspecs
~~~~~~~~~~~~~~~~~~~~~
---------------------

buildtest will send all valid buildspecs to **build** phase which is responsible for building
a shell-script from the buildspec file. In this stage, we create a **Builder** object
Expand All @@ -57,7 +54,7 @@ of failure, buildtest will raise an exception and buildspec will be ignored. The
stage

Running Buildspecs
~~~~~~~~~~~~~~~~~~~~
---------------------

In this stage, we run the test based on :ref:`executors <configuring_executors>` defined in configuration file. buildtest will
select the executor defined by ``executor`` property in buildspec which is responsible for running the test. There is a `BaseExecutor <https://github.com/buildtesters/buildtest/blob/devel/buildtest/executors/base.py>`_
Expand Down
Loading

0 comments on commit 006b43e

Please sign in to comment.