- 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.
17 lines
648 B
Gherkin
17 lines
648 B
Gherkin
Feature: The --addrepo commandline option.
|
|
|
|
Background:
|
|
Given an unique mock namespace
|
|
And pre-intitialized chroot
|
|
|
|
Scenario: Test that --addrepo works
|
|
Given a custom third-party repository is used for builds
|
|
When a build is depending on third-party repo requested
|
|
Then the build succeeds
|
|
|
|
Scenario: Test that --addrepo LOCAL_DIR works
|
|
Given a created local repository
|
|
And the local repo contains a "always-installable" RPM
|
|
And the local repo is used for builds
|
|
When a build which requires the "always-installable" RPM is requested
|
|
Then the build succeeds
|