Openbmc archive mirror
 help / color / mirror / Atom feed
From: GEORGE KEISHING <gkeishin@in.ibm.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: OpenBmc Test Repository:  Legacy REST support sunset Year end
Date: Thu, 7 Dec 2023 15:13:35 +0000	[thread overview]
Message-ID: <DM4PR15MB62561A7561E6085EECD801B8E68BA@DM4PR15MB6256.namprd15.prod.outlook.com> (raw)
In-Reply-To: <DM6PR15MB3676185D31E6DA488FA02ED5E6EDA@DM6PR15MB3676.namprd15.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]

Greetings,

As planned, new branch created https://github.com/openbmc/openbmc-test-automation/tree/v4.0-stable

Release Note:
https://github.com/openbmc/openbmc-test-automation/releases/tag/v4.0-stable

As communicated earlier, the expected changes on latest master will follow starting next year but in phases gracefully.
- Remove tools and codes supports which are no longer relevant (refer above release note if you still need it )
- Update/revisit documentation README and other information as part of the activity to maintain the relevant data
- Consolidation / Grouping of test suites/files to minimize clutter test directories across the repository
- Disable Legacy Rest and default to Redfish ONLY and remove flows which we had to support both in code
- Continue to update codes are per new changes in Robot and Python version available.

For more information you can reach us out on OpenBMC discord https://discord.gg/8rvZJQbE      #test-automation (https://discord.gg/4G3vd5rP )

Regards
George Keishing

From: GEORGE KEISHING
Sent: Friday, September 8, 2023 1:15 PM
To: openbmc@lists.ozlabs.org
Subject: OpenBmc Test Repository: Legacy REST support sunset Year end

Hi All,

               We are deprecating legacy REST test codes and to discontinue tools used in OpenBMC test this year end. We will branch out as a checkpoint if any users still want to use it in their environment.

               Post we branch out; we will start scrubbing off test code and some significant changes in the test layout and consolidate overall the test repository.

               Thank you for your support, feedbacks, and contribution to the test.

Regards
George Keishing


[-- Attachment #2: Type: text/html, Size: 8006 bytes --]

      reply	other threads:[~2023-12-07 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08  7:44 OpenBmc Test Repository: Legacy REST support sunset Year end GEORGE KEISHING
2023-12-07 15:13 ` GEORGE KEISHING [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM4PR15MB62561A7561E6085EECD801B8E68BA@DM4PR15MB6256.namprd15.prod.outlook.com \
    --to=gkeishin@in.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).