Comment 7 for bug 878832

On Mon, 31 Oct 2011 13:56:58 -0000, Paul Larson <email address hidden> wrote:
> That's probably ok, as long as we are pretty sure that we wouldn't have
> an *unrelated* job with the same job name. That's unlikely to happen
> here, not sure about other cases.

Ah yes this is what happens when I write emails when super tired on
planes: I forget things.

I regard the issue of multiple jobs with the same ID to fall into the
"if you break it you get to keep both pieces" sort of thing.

> Does this help them pull in the results to the build page though? or
> just link to them?

In the implementation I had in mind it would do both. Instead of
hitting

  $scheduler/$job_id/json

to get the bundle link as it does today, the page would hit something
like:

  $scheduler/+by-job-name/$job_name/json

which would return a link to the results of the most recent job with
that name.

> I was thinking if they had a button they clicked to resubmit the job, it
> would just resubmit the original job and get back a new job id that
> could be used the same way as before to reference the results. This
> could be appended to the existing results on the build page, or replace
> it, which ever their preference.

Yeah, that could work. I guess I tend to regard the build artifacts
as immutable -- although that's not strictly speaking the case.

Cheers,
mwh