Skip to content

Commit

Permalink
Move to tnf v4.5.5 (#42)
Browse files Browse the repository at this point in the history
  • Loading branch information
@ramperher
ramperher authored Nov 10, 2023
1 parent c7c1949 commit 498f196
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion roles/cnf_cert/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ tnf\_stage | "tests"
tnf\_check\_commit\_sha | false | Flag that allows to check if the tnf image used is based on the same commit SHA than the repository cloned in this role.
test\_network\_function\_repo | https://github.com/test-network-function/cnf-certification-test | Repository to download the tnf code.
test\_network\_function\_src\_dir | undefined | If testing a cnf-certification-test PR, this variable will be injected from test-runner scripts (used in dci-pipeline and dci-openshift-agent projects) to refer to the file path where the code from the PR is placed in the jumphost, so that it can be used in cnf_cert role to build a new tnf container image based on that code
test\_network\_function\_version | v4.5.4 | CNF Cert Suite version downloaded. DCI App Agent supports the latest stable version. HEAD version (in the main branch) can be also used, but it is not guaranteed a complete compatibility with the latest unstable changes. The versions prior to v4.0.0 are not compatible with the agent. Note that, starting from v4.1.6 (also with HEAD branch), tnf will also launch Preflight from CNF Cert Suite (included in `common` label until `v4.2.2`; from `v4.2.3` in advance, you need to explicitly use `preflight` label).
test\_network\_function\_version | v4.5.5 | CNF Cert Suite version downloaded. DCI App Agent supports the latest stable version. HEAD version (in the main branch) can be also used, but it is not guaranteed a complete compatibility with the latest unstable changes. The versions prior to v4.0.0 are not compatible with the agent. Note that, starting from v4.1.6 (also with HEAD branch), tnf will also launch Preflight from CNF Cert Suite (included in `common` label until `v4.2.2`; from `v4.2.3` in advance, you need to explicitly use `preflight` label).
test\_network\_function\_project\_name | cnf-certification-test | Directory name to look at on the tnf repo.
tnf\_labels | `"common,telco,extended"` | (This is the recommended way of selecting/skipping test suites starting from CNF Cert Suite v4.1.0, and the only supported method since tnf v4.3.4) List of [test suites](https://test-network-function.github.io/cnf-certification-test/test-spec/#available-test-specs) that are executed/skipped using labels. In particular, `tnf_labels` content must follow [these guidelines](https://onsi.github.io/ginkgo/#spec-labels), then dci-openshift-app-agent uses this string to run the tnf container with `-l` argument. Note that, when using labels, apart from using the tnf suite names as labels, you can also use, among others, `common` label to refer to all the stable tnf suites, `telco` label to include Telco-related tests (starting in v4.3.0), `extended` to new features added in v4.1.0, and `preflight` to run preflight on tnf. See the [cnf-certification-test README](https://test-network-function.github.io/cnf-certification-test/test-container/#run-the-tests) for more information, and also, check [CATALOG.md](https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md) to see the list of test suites available with the label that corresponds to each of them.
tnf\_suites | "" | (WARNING: this option is not supported since tnf v4.3.4. Also, it is not the recommended option to list test suites starting from CNF Cert Suite v4.1.0. Use `tnf_labels` instead) List of [test suites](https://test-network-function.github.io/cnf-certification-test/test-spec/#available-test-specs) that are executed. In particular, `tnf_suites` content must be the list of suites to be run, space separated (can be test suites and/or individual tests), so that dci-openshift-app-agent uses this string list to run the tnf container with `-f` argument. See the [cnf-certification-test README](https://github.com/test-network-function/cnf-certification-test/tree/v4.0.2#run-the-tests) for more information.
Expand Down
4 changes: 2 additions & 2 deletions roles/cnf_cert/defaults/main.yml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
tnf_stage: "tests"
tnf_check_commit_sha: false
test_network_function_repo: https://github.com/test-network-function/cnf-certification-test
test_network_function_version: v4.5.4
test_network_function_version: v4.5.5
test_network_function_project_name: cnf-certification-test
tnf_suites: ""
tnf_skip_suites: ""
Expand All @@ -27,7 +27,7 @@ tnf_image_suffix: "{{ lookup('community.general.random_string', length=16, speci
# Provide feedback for each tnf test launched. Just copy this template in your pipeline file and fill the value for the
# tests you want to provide feedback. You don't need to include the tests that you don't want to provide feedback.
# To insert line breaks, use \\n (you need to escape it). Same for quotes and so on.
# List of tests updated until tnf v4.5.4
# List of tests updated until tnf v4.5.5
tnf_feedback:
access-control-bpf-capability-check: ""
access-control-cluster-role-bindings: ""
Expand Down

0 comments on commit 498f196

Please sign in to comment.