A handy hack:
While testing out the first several modules in a pipeline, I don't want to progress to the remaining modules. If it makes it through the first 5, I want it to jus stop after that.
I don't want to take the time to comment out all remaining modules and later un-comment them.
So, in the config file, after my modules of interest, I added a stop:
#BioModule biolockj.module.diy.GenMod AS STOP
STOP.launcher=/bin/bash
STOP.scriptPath=./stop.sh
The file stop.sh:
#! /bin/bash
exit 1
The non-zero exit causes BioLockJ to treat this module as "failed" thus stopping the pipeline.
This was so handy, I think it would be worth while to have a minimalist module that does just this, so the config file would just have this stop line after my modules of interest:
#BioModule biolockj.module.Stop
This minimalist module takes no parameters, is a script module, but makes no scripts. In check dependencies it checks nothing, just prints a warning saying that it absolutely will fail, truncating the pipeline. Its execute task is to throw an Exception that ends the pipeline.
This basically is the "ConfigToFail" module from the test suite, but without even that much configuration.
A handy hack: While testing out the first several modules in a pipeline, I don't want to progress to the remaining modules. If it makes it through the first 5, I want it to jus stop after that. I don't want to take the time to comment out all remaining modules and later un-comment them.
So, in the config file, after my modules of interest, I added a stop:
The file stop.sh:
The non-zero exit causes BioLockJ to treat this module as "failed" thus stopping the pipeline.
This was so handy, I think it would be worth while to have a minimalist module that does just this, so the config file would just have this stop line after my modules of interest:
This minimalist module takes no parameters, is a script module, but makes no scripts. In check dependencies it checks nothing, just prints a warning saying that it absolutely will fail, truncating the pipeline. Its execute task is to throw an Exception that ends the pipeline.
This basically is the "ConfigToFail" module from the test suite, but without even that much configuration.