Improve CI job triggering rules
- Automatically start jobs for all images potentially affected by a Dockerfile template change or a Packer source file modification. The rationale here is that most meaningful changes to image contents happen through modifications to Dockerfile templates and Packer source files while Makefile updates are rare (and starting all relevant jobs when a Makefile is modified would be reckless). - Allow all jobs to be run (on demand) for pipelines created through the web interface. This allows any build job to be tested before merging a branch which modifies Makefile(s) but does not touch any Dockerfile templates or Packer source files (since Makefile changes alone do not trigger build jobs). - Automatically push rebuilt images to the production Docker registry when a branch is merged into "master". Propagating changes introduced by branches which only touch Makefile(s) will require creating a pipeline for the "master" branch using the web interface, but that is expected to be needed rarely. - Ensure scheduled build jobs are still run automatically.
Showing with 225 additions and 5 deletions