* Addressing breaking changes in migration from Nim 0.18 to 0.19.
* Finishing the initial pass at the refactor required to include
docker-based builds.
* Regaining confidence in the existing functionality by getting all
tests passing again after docker introduction (still need new tests to
cover new docker functionality).
* Output from the main strawboss executable is properly directed to stdout
and stderr.
* Added threshold logging to strawboss core functions.
* Fixed a bug in the way dependent steps were detected and executed.
The logic for checking if prior steps had already been executed was only
executed once when the initial step was prepared, not for any of the
dependent steps. This logic has been moved into the main work block for
executing steps.
* Renamed `initiateRun` to `run` and `runStep` to `doRun` to be more accurate.
* Dependent steps get their owng, independent copy of the workspace.
* Updated the test project to provide a test target.
* Rename artifactsRepo -> buildDataDir to be more explicit about the fact that
it holds more than just the artifacts.
* Revert removal of run ids.
* Move Worker definition into core as part of making the core responsible for
accepting run requests.
* Make the core module more responsible for internal details of data structure
and storage. External callers should not need to construct paths to
artifacts, versions, etc. but should be able to call method in the core
module to do this work for them.
* The working directory no longer contains anything but the checked-out code.
All StrawBoss-specific data is stored by StrawBoss elsewhere.
* Add a regular maintenance cycle to the server module.
StarBoss is meant for building things checked into the repo It is also designed
around repeatable builds. So it makes the assumption that running a build step
for a specific version of a project will always result in the same output. So
runs are identified by the project, build step, and version.
We were expecting to find the path to the `strawboss` binary implicitly from
the environment, which meant that configuration was also implicit, and required
more setup. Now the path to the binary is explicit in the StrawBoss runtime
configuration, and the path to the configuration file can also be explicitly given.
* Split the `test` nimble task into `unittest` and `functest`, with
corresponding test directories and test runners.
* Added documentation in README regarding building and testing StrawBoss.
* Created a small, simple test project for use in the functional tests.
* Added a `keepEnv` template in the server unit test code to make it easy to
preserve the working environment for a single unit test to invistigate
failures manually.
