Skip to content
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

ci: Run cockpit tests in PRs #2

Closed
wants to merge 5 commits into from
Closed

ci: Run cockpit tests in PRs #2

wants to merge 5 commits into from

Conversation

martinpitt
Copy link
Owner

@martinpitt martinpitt commented Aug 2, 2023

@martinpitt
Copy link
Owner Author

Cool, works! 👍 Next experiment, break SELinux at a tactical place and verify that it breaks our tests.

@martinpitt martinpitt force-pushed the revdeps branch 2 times, most recently from e742f12 to f0294e9 Compare August 3, 2023 06:06
@martinpitt martinpitt force-pushed the packit-build branch 2 times, most recently from 5279188 to edb6506 Compare August 4, 2023 09:46
Teach make-srpm.sh to support building a directory with the sprm
ingredients (the unpacked directory) to become compatible with the
packit workflow. This mostly obsoletes the need of doing custom COPR
builds, so eventually .copr/ can be simplified. But keep the old
functionality for the time being.

Note that this way of building an srpm in packit is still rather
unusual: the normal mode is to maintain the .spec and all auxiliary
files in the upstream git; that then enables automatic Fedora releases,
and make it easier to keep the spec in sync. But one step after
another..

Configure packit to automatically build srpm and rpms in the usual
temporary COPRs. This makes it much easier to test PRs both by humans
and future integration tests. There are no test plans yet, but already
enable the TF run to at least cover package installation/upgrade.

Run these on Rawhide and the current stable Fedora (38 right now).

This entirely replaces the "build-rpm" workflow, so drop that.
See https://cockpit-project.org/blog/tmt-cross-project-testing.html

Drop the install-only tests, as TF only runs the default "install check"
test if there are no plans, but now we have one. That will cover the
installation/upgrade as preparation step.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant