forked from fedora-selinux/selinux-policy
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
martinpitt
force-pushed
the
packit-build
branch
from
August 2, 2023 12:42
dcfc66a
to
df48105
Compare
martinpitt
force-pushed
the
revdeps
branch
2 times, most recently
from
August 2, 2023 13:24
38578f4
to
73029d7
Compare
Cool, works! 👍 Next experiment, break SELinux at a tactical place and verify that it breaks our tests. |
martinpitt
force-pushed
the
revdeps
branch
2 times, most recently
from
August 3, 2023 06:06
e742f12
to
f0294e9
Compare
martinpitt
force-pushed
the
packit-build
branch
2 times, most recently
from
August 4, 2023 09:46
5279188
to
edb6506
Compare
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.
martinpitt
force-pushed
the
packit-build
branch
from
August 8, 2023 04:06
edb6506
to
fbfa187
Compare
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.
martinpitt
force-pushed
the
packit-build
branch
from
August 8, 2023 12:18
fbfa187
to
a571063
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See https://cockpit-project.org/blog/tmt-cross-project-testing.html
Goes after fedora-selinux#1820