Project

General

Profile

Actions
Copy link

action #130940

open

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

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

Trigger openQA tests mentioned in github comments as part of automatic testing as well - trusted group "tests-maintainer" only size:M

Added by okurz 11 months ago. Updated 2 days ago.

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

0%

Estimated time:

Description

Motivation

Follow-up to #130934. After having openQA CI integration which reads github pull request description and triggers according openQA clone jobs github comments created or updated should be considered the same.

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 comments
  • AC2: Ensure openQA documentation covers that also github comments are parsed and how to use that
  • AC3: An update to the PR code does not retrigger any openQA jobs mentioned in comments
  • AC4: Comments created/edited by anyone not in the group "tests-maintainer" are ignored

Suggestions

  • Wait for #130934
  • Read what was done originally in #63712 and the according pull request to openQA https://github.com/os-autoinst/openQA/pull/2618 and also #130934
  • Check if openqa-clone-custom-git-refspec with special comments also covers github comments or only the initial description
  • Extend the existing approach where necessary
  • Ensure that the same process is triggered also on comment updates
  • Only look at comments created/edited by members of the group "tests-maintainer" for security reasons
Actions
Copy link
 #1

Updated by okurz 10 months ago

  • Target version changed from Ready to future
Actions
Copy link
 #2

Updated by okurz about 2 months ago

  • Target version changed from future to Tools - Next
Actions
Copy link
 #3

Updated by okurz about 1 month ago

  • Target version changed from Tools - Next to Ready
Actions
Copy link
 #4

Updated by okurz about 1 month ago

  • Subject changed from Trigger openQA tests mentioned in github comments as part of CI as well to Trigger openQA tests mentioned in github comments as part of automatic testing as well
  • Description updated (diff)
  • Assignee set to okurz

we couldn't agree on this yet during estimation and I will follow-up with the team in more detail about the general idea if it makes sense like that or not at all.

Actions
Copy link
 #5

Updated by okurz 23 days ago

  • Target version changed from Ready to Tools - Next
Actions
Copy link
 #6

Updated by okurz 5 days ago

  • Subject changed from Trigger openQA tests mentioned in github comments as part of automatic testing as well to Trigger openQA tests mentioned in github comments as part of automatic testing as well - trusted group "tests-maintainer" only
  • Description updated (diff)
  • Assignee deleted (okurz)
  • Target version changed from Tools - Next to Ready
Actions
Copy link
 #7

Updated by jbaier_cz 2 days ago

  • Subject changed from Trigger openQA tests mentioned in github comments as part of automatic testing as well - trusted group "tests-maintainer" only to Trigger openQA tests mentioned in github comments as part of automatic testing as well - trusted group "tests-maintainer" only size:M
Actions
Copy link
 #8

Updated by jbaier_cz 2 days ago

  • Status changed from New to Workable
Actions
Copy link

Also available in: Atom PDF