**Steps to replicate the issue** (include links if applicable):
* Make a change which causes the image to be rebuilt
**What happens?**:
The component that 'owns' the job gets re-created in jobs (restarted)
**What should have happened instead?**:
All components referencing the job should get re-created in jobs (restarted)
**Other information** (browser name/version, screenshots, etc.):
Example:
```
tools.cluebotng-monitoring@tools-bastion-13:~$ toolforge components deployment show
Warning: You are using a beta feature of Toolforge.
Deployment ID: 20250829-162852-u3l0smc04s
Created: 20250829-162852
Status: successful
Long status:
Finished at 2025-08-29 16:31:31.204940
Builds:
alertmanager(skipped): id:no-build-needed Component re-uses build from prometheus
blackbox-exporter(skipped): id:no-build-needed Component re-uses build from prometheus
checker(skipped): id:cluebotng-monitoring-buildpacks-pipelinerun-bqqsv Reusing existing build
grafana(skipped): id:no-build-needed Component re-uses build from prometheus
prometheus(successful): id:cluebotng-monitoring-buildpacks-pipelinerun-v2j52 You can see the logs with `toolforge build logs cluebotng-monitoring-buildpacks-pipelinerun-v2j52`
wiki-update-receiver(skipped): id:no-build-needed Component re-uses build from prometheus
Runs:
alertmanager(successful): [info] (Job alertmanager is already up to date)
blackbox-exporter(successful): [info] (Job blackbox-exporter is already up to date)
checker(successful): [info] (Job checker is already up to date)
grafana(successful): [info] (Job grafana is already up to date)
prometheus(successful): [info] (Job prometheus created)
wiki-update-receiver(successful): [info] (Job wiki-update-receiver created)
```