Project

General

Profile

action #54311

action #37958: [epic] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule

[functional][y] Implement hint to trigger VR for staging in case modules used there are changed in the PR

Added by riafarov 12 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
SUSE QA tests - Milestone 30+
Start date:
2019-07-16
Due date:
2019-09-10
% Done:

0%

Estimated time:
8.00 h
Difficulty:
Duration: 41

Description

Motivation

We have figured out that we can have a bot which posts messages in the PR using tokens.
Also now, we have staging tests in the yaml format, so we know exactly which modules are used there.
Consequently, we can put the message that VR for staging are required in case any of these modules was changed.

We have jenkins instance, where we can run the bot, or use one of the personal servers.

Acceptance criteria

  1. There is warning/info message in each PR in case it introduces changes to any of the modules executed in staging

Further info

From the last time we have learned that with api we can put messages on PR, whereas we could not store tokens.

There is https://ci.suse.de/ instance we can use.

List of the modules used in the staging https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/schedule/staging

More reading: https://embeddedartistry.com/blog/2017/12/21/jenkins-kick-off-a-ci-build-with-github-push-notifications

We don't know how easy it will be to get list of the modified files.

History

#1 Updated by riafarov 12 months ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 8.00 h

#2 Updated by JERiveraMoya 12 months ago

  • Due date changed from 2019-08-13 to 2019-08-27

#3 Updated by riafarov 11 months ago

  • Due date changed from 2019-08-27 to 2019-09-10

#4 Updated by oorlov 11 months ago

  • Status changed from Workable to In Progress
  • Assignee set to oorlov

#5 Updated by oorlov 10 months ago

  • Status changed from In Progress to Resolved

Follow-up ticket created. All the investigations are listed there: https://progress.opensuse.org/issues/56495

Also available in: Atom PDF