I am wondering about this:
we are all used to continuous build. I.e. every push of source code to a version control system triggers a build job on a build system (Jenkins, GitLab CI/CD, whatever, ...) that builds the source code. Builds produce artifacts, usually libraries (jar files, dll files, whatever ...) that are pushed to an artifact storage (Nexus, artifactory, GitLab package registry, whatever ...).
Then builds trigger other builds of components that depend on the just created artifacts. This in turn triggers further builds up the software dependency hierarchy.
Q: why do only updates of source code trigger builds jobs, but updates of artifacts in an artifact store don't? Is there a specific reason?
At least the environment I'm used to (Jenkins, GitLab CI/CD, Nexus, GitLab package registry) works like that.
Q: are there other environments (build automation systems, artifact stores, whatever, ...) that include job triggers by any artifact update?