-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[v5.4-rhel] e2e tests with TMT #26316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v5.4-rhel
Are you sure you want to change the base?
Conversation
This reverts commit 64aaa45. Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
72f97ba
to
bae53aa
Compare
No rpms are built, tests are run directly on binaries built from Makefile targets. RHEL environments are provisioned on internal testing farm. Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
110bae0
to
3781fdd
Compare
Include system and integration tests in the same file, get rid of tags and filter by plan name. Adjust names and identifiers for consistency. Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
Drive-by comment: This is clearly a huge undertaking, and overall will become a necessity. However, that doesn't mean it has to be all done at once. Remember even the Cirrus-CI setup didn't happen in a day (or single PR). It came together bit by bit over a few years, with at least one or two major re-writes as more pieces were bolted on. Have you considered a more piecemeal approach for TMT/TF? For example, maybe try just replacing the rootfull system tests on a single architecture. |
Ack, I've suspended this until we find the right place for RHEL branch hosting. These should ideally be tested with the binaries built from the rpm, and that's blocked on not being able to fetch rhel specs outside of the internal network. CentOS Stream specs don't quite cut it as they may not be in sync with RHEL and hosting a spec in src-git could end up rotting as it's not used directly in RHEL rpm (unlike Fedora which gets spec from upstream with Packit). |
Ahh right, yes, this makes perfect sense. I agree, let's solve the RHEL branch hosting problem first. |
Does this PR introduce a user-facing change?