- Add mock-specific build artifacts (chroot/, mock-*, mockroot/) - Include package build files (*.deb, *.changes, *.buildinfo) - Add development tools (.coverage, .pytest_cache, .tox) - Include system files (.DS_Store, Thumbs.db, ._*) - Add temporary and backup files (*.tmp, *.bak, *.backup) - Include local configuration overrides (config.local.yaml, .env.local) - Add test artifacts and documentation builds - Comprehensive coverage for Python build system project This ensures build artifacts, chroot environments, and development tools are properly ignored in version control.
19 lines
716 B
Gherkin
19 lines
716 B
Gherkin
Feature: The chroot_scan plugin
|
|
|
|
@chroot_scan
|
|
Scenario: Check that chroot_scan works and file permissions are correct
|
|
Given chroot_scan is enabled for dnf5.log
|
|
And an unique mock namespace
|
|
When an online source RPM is rebuilt
|
|
Then the build succeeds
|
|
And dnf5.log file is in chroot_scan result dir
|
|
And ownership of all chroot_scan files is correct
|
|
|
|
@chroot_scan
|
|
Scenario: Check that chroot_scan tarball is created correctly
|
|
Given an unique mock namespace
|
|
And chroot_scan is enabled for dnf5.log
|
|
And chroot_scan is configured to produce tarball
|
|
When an online source RPM is rebuilt
|
|
Then the build succeeds
|
|
And chroot_scan tarball has correct perms and provides dnf5.log
|