Project

General

Profile

action #43580

[sle][functional][y] The RT product can be tested by release managers or developers before full SLE validation

Added by okurz over 1 year ago. Updated over 1 year ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Target version:
Start date:
2018-11-05
Due date:
% Done:

0%

Estimated time:
Duration:

Description

Motivation

[08/11/2018 09:04:36] <okurz> riafarov, oorlov: regarding the RT bug about devel_basis and such, would be great if Jeffrey could have tested in before. I don't see why we need to do the rather trivial check of "does it even resolve dependencies". WDYT?
[…]
[08/11/2018 10:06:05] <riafarov> okurz: sure, if we could improve the process there it would be great. As of now I believe we played it safe as we haven't planned to dedicate whole sprint to RT before getting blocked

Acceptance criteria

  • AC1: changes in the package 000product can be tested before a submit request is accepted into any staging project

Suggestions

  • Can media be created locally by devs e.g. using something like "mksusecd"? See https://github.com/shundhammer/huha-linux-tips/blob/master/doc/yast-devel-tips.md#duds-and-isos
  • Research how media can be created e.g. in development or home projects, how other release managers test something before "complete build validation"
  • Document somewhere or reference existing documentation how changes in the package 000product can be tested before a submit request is accepted into any staging project
  • Optional: Provide helper scripts to ease the job

Related issues

Copied from openQA Tests - action #43373: [sle][functional][y] Add installation test scenario for RT productResolved2018-11-052018-12-04

Copied to QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15Workable2018-11-05

History

#1 Updated by okurz over 1 year ago

  • Copied from action #43373: [sle][functional][y] Add installation test scenario for RT product added

#2 Updated by okurz over 1 year ago

talked shundhammer today and he confirmed that "mksusecd" or "mkdud" is the way to go

#3 Updated by okurz over 1 year ago

As we learned with release managers we seem to run around in circles a bit, multiple project managers just pointing to each other until we reach the beginning ;)

One possibility mentioned was setting up staging tests for RT even though not the only choice. As a reference https://openqa.suse.de/tests?match=rt-product mentions the openQA tests we have for "build validation" on SLE15SP1, e.g. https://openqa.suse.de/tests/2280268

coolo wants to handle it.

#4 Updated by coolo over 1 year ago

I added rt-product to staging:a - but ADDURL is miscalculated: https://openqa.suse.de/tests/2282667#

#5 Updated by okurz over 1 year ago

  • Copied to action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15 added

#6 Updated by okurz over 1 year ago

  • Estimated time deleted (5.00 h)

The wrong selection of modules is coming from the variable definition for WORKAROUND_MODULES on all staging media on https://openqa.suse.de/admin/products which is most likely only valid for SLES, not other SLE products.

coolo I suggest to remove the scenario again from staging project(s) until we have clarified the value and effort. As this ticket here was originally – and should still be – about "How can the RM of RT test his own changes" I am separating the "add staging project" into #44393

#7 Updated by okurz over 1 year ago

  • Description updated (diff)

#9 Updated by okurz over 1 year ago

  • Due date set to 2019-02-12

pre-fill last sprint in M22 with all tickets within milestone not yet assigned to sprints

#10 Updated by okurz over 1 year ago

  • Description updated (diff)
  • Status changed from New to Workable

#11 Updated by riafarov over 1 year ago

  • Due date deleted (2019-02-12)

Again, is it well communicated with Jeffrey. From the ticket I see two of us have came up with something. I personally have no interest in driving and establishing full release cycle for the RT, but rather support RM if there is any request.

Also, seems to duplicate #44393 partly.

#12 Updated by okurz over 1 year ago

  • Target version changed from Milestone 22 to future

riafarov wrote:

Again, is it well communicated with Jeffrey. From the ticket I see two of us have came up with something. I personally have no interest in driving and establishing full release cycle for the RT, but rather support RM if there is any request.

Well, sure, let's do this. I see we with our QA view can provide the best value by helping development setting up a product development chain including automated tests when we already have expertise in this area. But why did you move it out of the sprint then? So I move it to "future" and we can clarify this first and then plan accordingly.

Also, seems to duplicate #44393 partly.

No, it's not. You can read #44393 which I cloned it from. Because our initial idea was turned into "We just need a staging test" which is not covering all.

Also available in: Atom PDF