Allow package steps to specify files that impact their output. This is used as a heuristic for rebuilding packages during pull requests. Currently this includes the build.toml file, and control and instructions files for nipkg steps.
Why should this Pull Request be merged?
We currently either have to manually force packages to be built when testing, or blindly submit code and wait for a release branch to pick it up. This should give us more confidence when reviewing changes, without building packages for every change.
What testing has been done?
I've built a few pull requests that both do and do not trigger installer builds; I intend to test it on Routing and Faulting (which builds multiple packages) before submitting.
What does this Pull Request accomplish?
Allow package steps to specify files that impact their output. This is used as a heuristic for rebuilding packages during pull requests. Currently this includes the
build.toml
file, andcontrol
andinstructions
files for nipkg steps.Why should this Pull Request be merged?
We currently either have to manually force packages to be built when testing, or blindly submit code and wait for a release branch to pick it up. This should give us more confidence when reviewing changes, without building packages for every change.
What testing has been done?
I've built a few pull requests that both do and do not trigger installer builds; I intend to test it on Routing and Faulting (which builds multiple packages) before submitting.