robojerk
4c0dcb2522
- 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
921 B
Gherkin
19 lines
921 B
Gherkin
Feature: Mock 5.7+ supports hermetic builds
|
|
|
|
@hermetic_build
|
|
Scenario: Hermetic build against a DNF5 distribution
|
|
Given an unique mock namespace
|
|
When deps for python-copr-999-1.src.rpm are calculated against fedora-rawhide-x86_64
|
|
And a local repository is created from lockfile
|
|
And a hermetic build is retriggered with the lockfile and repository
|
|
Then the build succeeds
|
|
And the produced lockfile is validated properly
|
|
|
|
@hermetic_build
|
|
Scenario: Hermetic build against a DNF4 distribution
|
|
Given an unique mock namespace
|
|
When deps for mock-test-bump-version-1-0.src.rpm are calculated against centos-stream+epel-9-x86_64
|
|
And a local repository is created from lockfile
|
|
And a hermetic build is retriggered with the lockfile and repository
|
|
Then the build succeeds
|
|
And the produced lockfile is validated properly
|