And, if you restart a job, no new entry is made for the job history, so it just overwrites the job history on rerun. This is likely because they modeled the jo

And, if you restart a job, no new entry is made for the job history, so it just overwrites the job history on rerun. This is likely because they modeled the jobs as one-per-job-def-and-commit, so they don't have a UX to show two. This is a security blind spot, since you can do something naughty in a job, then rerun it and the logs are no longer accessible.