Use docker host network for containers If vuls or lynis are told to test the same host where they're running (and it's only reachable via localhost) then having the containers in the host network will provide reachability to localhost so vuls/lynis can run their tests. Change-Id: I70c6975676facb6de41790928a5d810a43e273d6 Signed-off-by: Igor D.C <igordcard@gmail.com>
Fix blucon.py argument issue Change argument -p in -P to synchronize validation/bluval/blucon.py with ci-management/jjb/shell/run_bluval.sh arguments Signed-off-by: DANIEL STOICA <daniel.stoica@enea.com> Change-Id: I53ee0751e924cc0f9c382364658eecd540848aa5
blucon: Add argument '-p' for pulling latest tag If `--pull` or `-p` argument is passed to blucon, it will now run a `docker pull` command prior to launching the testcases with `docker run`. This should prevent the testcases from using stale docker images if already present on the machine. JIRA: VAL-107 Change-Id: Id4b7947a0de7abf07f69812c6deef71919b9041a Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
blucon.sh: Allow validation/results dir override When running in CI, the validation git repository is cloned in the job workspace, which usually has a custom directory name matching the job name (e.g. bluval-daily-master) instead of the previously hardcoded 'validation' directory name. Also, the results dir should not be a sibling of the validation git repo directory when running in CI, but a subdirectory of the said dir. To accomodate this, allow overriding both previously hardcoded directory paths via environment variables (VALIDATION_DIR, RESULTS_DIR). While at it, add a new '-t' argument for specifying the Docker tag to be used for the validation docker images (previously hardcoded to 'latest') in order to support running docker images associated to a specific Validation release tag (e.g. 3.0.0). JIRA: VAL-95 Change-Id: I4d3c10881de28c64bcca05ff23aa1025f67a1f5e Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
bluval: Add Jenkins log-parser rules Instead of creating the log-parser rules on the fly from the CI job, add the rules to the current repository, allowing the Validation committers to tweak them independently (not through ci-management changes). While at it, extend and improve the previous rules by: - raising a warning instead of an error for robot FAIL messages (which will later be changed via ci-management to _not_ fail the CI job run); - separating the test suites into log parsing sections; - raising an info for PASS robot messages (so they are listed in the log-parser links section for better readability); - fail the CI job only if critical tests failed; For logparser section grouping to work as expected, fix one output buffering issue that used to print the issued commands after their output (and also fix another output buffering related issue to keep things uniform). JIRA: VAL-104 Change-Id: I1506d84a44926e80913562f67f24885a98f94df7 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Prevent python to write .pyc files on import JIRA: VAL-94 Change-Id: I3bf6dd55cb510e2d9a2704369a1bd0599b48eb63 Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
Convention over configuration Jira: [VAL-83] bluva.py is taking varibles.yaml and writing updated version to varibles_updated.yaml varibles_updated.yaml is passed to robot framework. OperatingSystem.Get Environment is better than $HOME. Each container automatically removed Each test suite has a debug.log by default Signed-off-by: Naga Sugguna <ns156u@att.com> Change-Id: Iae95d1ee12c8c5e44949be3faf5b0fc9fc40266e
Add a new parameter to blucon script Jira: [VAL-72] Add a parameter which specifies container network. Signed-off-by: valentin.radulescu <valentin.radulescu@enea.com> Change-Id: I9defc4a122db4c4f6309d4a98f29500849eeeeec
generate test_info.yaml Signed-off-by: Naga Sugguna <ns156u@att.com> Change-Id: I870a98af01e96213025ce2f989410efada677364
Customize the volume list per layer - Create an input yaml file for the list of volumes that will be mounted to the container when running the tests. - Customize the list of containers for each layer. - Add the posibility to store the bluval-<blueprint>.yaml file outside the validation project and mount it at runtime. Signed-off-by: Cristina Pauna <cristina.pauna@enea.com> Change-Id: Id3c21cb861879cd3040b06badfb9622429734ce6
[RECV-94] Separate docker/robot invoking Change-Id: I3dbeda2c11be09fbb250417042c6f76a01c92d0f Signed-off-by: Naga Sugguna <ns156u@att.com>