BLCI User Interface¶
The way to interact with BLCI is through the ./bl
driver script within the
BLCI root directory. Pass no argument to see help and options.
Initialize the repo¶
Once you have a blci.yml
configuration file in the root directory of your
repo/project (i.e., $PROJECT_HOME
) with at least the required configuration
settings language
, You can initialize the repo as
follows:
./bl -i $PROJECT_HOME
BLCI initialization performs two actions:
- Builds and saves the code dependency graph file
blci.deps
- Fleshes out a minimal
blci.yml
configuration file to a point to where a repo is a valid BLCI repo leaving thedata_deps
,script
and any other user-specific setting to be completed by the user.
NOTE: The default action is to append and overwrite the minimal
configuration file a user creates. The filename of the original
configuration file will change to blci.yml.old
. To change the overrwrite
behavior use the -n [--nooverwrite]
flag.
Add the repo¶
To add a repo execute:
./bl -a $PROJECT_HOME
A BLCI add
action:
- Creates a remote Github repo and tracks it using Travis CI (if the repo is untracked).
- Build the Travis metadata.
- Add, commit, push and Travis build your repo.
TODO: Undo¶
./bl -u $PROJECT_HOME
Undo the previous ./bl -a
(add) action and restore the repo to it’s previous state.
Build¶
Force a build of your BLCI repo without making changes to your code or using ./bl -a
. Execute:
./bl -b $PROJECT_HOME
Force a build action without changing any code within the repo.
Clean¶
To clean up all BLCI metadata and configuration files use the clean operation. This action deletes files so use with care.
./bl -c $PROJECT_HOME