Project

General

Profile

action #94249

action #93441: [sle][security][sle15sp4][CC] CC hand over

[sle][security][sle15sp4][CC] automation: figure out which code branch should be used and how to be used in openQA

Added by llzhao 6 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Spike/Research
Target version:
-
Start date:
2021-06-18
Due date:
% Done:

100%

Estimated time:
16.00 h
Difficulty:

Description

  1. Compare the "audit-test" code branches and figure out which is the latest/best branch to be used.
  2. Figure out how to access the branch in openQA environments.

History

#1 Updated by llzhao 6 months ago

Resolved.

  1. compared the 5 code branches under "https://gitlab.suse.de/security/cc-testing-sles15" and "https://gitlab.suse.de/security/audit-test-sle15" there are no big difference but "audit-test-sle15" is much more clean than others then we decided to use "audit-test-sle15" code branch.
    aarch64-audit-test
    amd-x64_64-audit-test
    intel-x64_64-audit-test
    z15-audit-test
    audit-test-sle15

  2. How to access the code branch in openQA
    Option 1: Public "audit-test-sle15" then "wget --no-check-certificate https://gitlab.suse.de/security/audit-test-sle15/-/archive/master/audit-test-sle15-master.tar" in openQA.
    Option 2: Put the test suite to smt server then "wget --no-check-certificate http://migration-smt2-1.qa.suse.de/audit-test-sle15-master.tar" in openQA.
    Option 3: Put the test suite to "https://gitlab.suse.de/openqa/os-autoinst-needles-sles"

"Option 1" and "Option 2" work now. "Option 3" is needless then.

#2 Updated by llzhao 6 months ago

  • Status changed from New to Resolved

Also available in: Atom PDF