Project

General

Profile

Actions

coordination #130850

closed

coordination #58184: [saga][epic][use case] full version control awareness within openQA

coordination #48641: [epic] Trigger openQA tests in pull requests of any product github pull request

[epic] Use openqa-clone-custom-git-refspec to parse github description+comments and trigger openQA tests as part of CI

Added by okurz about 1 year ago. Updated 16 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2023-06-15
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

Now we have a CI integration of openQA and pull requests on github can trigger openQA jobs and feed back the result. A challenge for big test matrices is to select which openQA jobs to execute. openqa-clone-custom-git-refspec for years can parse github description (and comments?) for openQA jobs to clone. That can now be integrated together to … be awesome

A comment like this or another format can be used in PR descriptions or commits to clone a job:

@openqa: Clone my/test/job/url

Acceptance criteria

  • AC1: openQA CI integration in any existing test distribution github project automatically runs openQA tests based on links to existing openQA jobs in the github description
  • AC2: openQA documentation explains how the CI integration in new test distribution github projects can be setup to run as in AC1
  • AC3: Same as AC1 but for any github comment
  • AC4: One is able to customize test scheduling with additional test parameters, e.g. @openqa http://my/openqa/t1 FOO=bar or @openqa BAR=eggs

Suggestions

  • Read what was done originally in #63712 and the according pull request to openQA https://github.com/os-autoinst/openQA/pull/2618
  • Try out openqa-clone-custom-git-ref with special comments
  • Document this feature somewhere
  • Additional test parameters specified are applied same as users are used to with openqa-clone-job - we don't expect to use the script but e.g. CloneJob.pm or refactor code as needed
  • Split individual ACs into separate tickets if implementation gets too time consuming
  • If you come up with something that works in a github workflow but becomes too big consider creating a github action repository or create an additional feature in our existing scripting

Subtasks 3 (0 open3 closed)

action #130934: Trigger openQA tests mentioned in github description as part of CI size:MResolvedmkittler2023-06-15

Actions
action #130940: Trigger openQA tests mentioned in github comments as part of automatic testing as well - trusted group "tests-maintainer" only size:MResolvedmkittler2023-06-15

Actions
action #130943: Test parameterization for github description/comments mentioned openQA job clones as part of CI size:SResolvedmkittler2023-06-15

Actions

Related issues 1 (0 open1 closed)

Related to openQA Project - action #63712: Have git-clone-custom-refspec pickup tests from PR descriptionsResolvedlivdywan2020-02-21

Actions
Actions #1

Updated by okurz about 1 year ago

  • Related to action #63712: Have git-clone-custom-refspec pickup tests from PR descriptions added
Actions #2

Updated by okurz about 1 year ago

  • Tracker changed from action to coordination
  • Subject changed from Use openqa-clone-custom-git-refspec to parse github description+comments and trigger openQA tests as part of CI to [epic] Use openqa-clone-custom-git-refspec to parse github description+comments and trigger openQA tests as part of CI
  • Description updated (diff)
  • Assignee set to okurz
Actions #3

Updated by okurz about 1 year ago

  • Status changed from New to Blocked
Actions #4

Updated by okurz 9 months ago

  • Target version changed from Ready to Tools - Next
Actions #5

Updated by okurz 16 days ago

  • Status changed from Blocked to Resolved
  • Target version changed from Tools - Next to Ready

All ACs fulfilled. All mentioned suggestions covered.

Actions

Also available in: Atom PDF