summaryrefslogtreecommitdiff
path: root/.travis.yml
diff options
context:
space:
mode:
authorMassimiliano Culpo <massimiliano.culpo@gmail.com>2019-03-29 00:56:36 +0100
committerPeter Scheibel <scheibel1@llnl.gov>2019-03-28 16:56:36 -0700
commit0a006351c8283b32c5ee5d13f8417875e534c377 (patch)
treea427e210ba8493a1119d20509b0bdff7abb4cd8b /.travis.yml
parentb2b91a1f00bb31bb1f794a3debe83a7352b4f48e (diff)
downloadspack-0a006351c8283b32c5ee5d13f8417875e534c377.tar.gz
spack-0a006351c8283b32c5ee5d13f8417875e534c377.tar.bz2
spack-0a006351c8283b32c5ee5d13f8417875e534c377.tar.xz
spack-0a006351c8283b32c5ee5d13f8417875e534c377.zip
Spack can be extended with external commands (#8612)
This provides a mechanism to implement a new Spack command in a separate directory, and with a small configuration change point Spack to the new command. To register the command, the directory must be added to the "extensions" section of config.yaml. The command directory name must have the prefix "spack-", and have the following layout: spack-X/ pytest.ini #optional, for testing X/ cmd/ name-of-command1.py name-of-command2.py ... tests/ #optional conftest.py test_name-of-command1.py templates/ #optional jinja templates, if needed And in config.yaml: config: extensions: - /path/to/spack-X If the extension includes tests, you can run them via spack by adding the --extension option, like "spack test --extension=X"
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions