|
|
Issue 0055 in split format
- Summary
- links in job descriptions show up in arbitrary order
; Owner: Tim
; Reporter: Tim
; Status: closed
; Priority: medium
|
; Summary: links in job descriptions show up in arbitrary order
; Owner: Tim
; Reporter: Tim
; Status: closed
; Priority: medium
|
|
|
= Description =
A Jenkins build page and job page shows links for each run.
|
|
The links for a run depend on whether the test succeeds or fails, and
on whether the spec for the run indicates extra links (for success or failure).
|
The links for a run depend on whether the test succeeds or fails, and
on whether the spec for the run indicates extra links (for success or failure).
|
|
The links are put there at job creation time by ftc.
|
The links are put there at job creation time by ftc.
|
|
For a normal test, the success links are:
* testlog run.json
and the failure links are:
* run.json devlog fuegolog testlog prolog
|
For a normal test, the success links are:
* testlog run.json
and the failure links are:
* run.json devlog fuegolog testlog prolog
|
|
Having these out of order is confusing.
|
Having these out of order is confusing.
|
|
Implement preferred sorting for links, such that known links occur
in a set order, and any unknown links occur alphabetically after that.
|
Implement preferred sorting for links, such that known links occur
in a set order, and any unknown links occur alphabetically after that.
|
|
Or change links to a list of tuples, so that it can be ordered in an array.
|
Or change links to a list of tuples, so that it can be ordered in an array.
|
|
|
= Notes =
This was resolved by adding some ordering logic to 'ftc add-jobs' code.
|
- backlink
Fuego Issues List
|
; backlink: [[Fuego Issues List]]
|
|
|