stackabletech / ci

Config files for Jenkins jobs ran by our infrastructure
2 stars 0 forks source link

Skip operator installation when running tests #108

Closed razvan closed 3 months ago

razvan commented 4 months ago

Description

The scripts/run_tests.sh has gained the ability to install operators needed for the integration tests it's self. This allows us to install different operator versions in PRs that address cross-cutting concerns:

▶ ./scripts/run_tests.sh --help
Unknown parameter : --help
  Usage:
     run_tests.sh [options]
  Options:
    --test-suite <test-suite>  Run a test suite from the test_definition.yaml file. Default is all tests.
    --test <test-name>         Run a specific test or a set of tests.
    --skip-delete              Skip resource deletion after the test run.
    --parallel <number>        Run tests in parallel. Default is to run all tests in parallel.
    --skip-release             Skip the operator installation.

To run the nightly tests from Jenkins use:

./scripts/run_tests.sh --test-suite nightly

Acceptance criteria

backstreetkiwi commented 3 months ago

Update as discussed w/ @razvan: We re-enable the dropdown for the operator version and pass the value to the test script (new version, written in Python)

backstreetkiwi commented 3 months ago

@razvan Can this ticket be closed? Thx.

razvan commented 3 months ago

@razvan Can this ticket be closed? Thx.

Could you please also add --log-level debug to the run-tests command ? This way we can see in the logs what version of the operators was actually installed. Thanks

backstreetkiwi commented 3 months ago

@razvan Can this ticket be closed? Thx.

Could you please also add --log-level debug to the run-tests command ? This way we can see in the logs what version of the operators was actually installed. Thanks

Done

razvan commented 3 months ago

Works. Thanks.