Specific fields of a report should be locked for following updates (eg. start_timestamp)

RESOLVED WONTFIX

Status

Product:
Tree Management
Component:
Treeherder: API
Status:
RESOLVED WONTFIX
Reported:
3 years ago
Modified:
10 months ago

People

(Reporter: whimboo, Unassigned)

Tracking

Details
(Reporter)

Description

•
3 years ago 
We submit reports for the states running and completed. Thereby we accidentally reset the start_timestamp when sending the completed report. Sadly the timestamp gets overwritten in Treeherder.

IMO some of the job properties should be locked when it comes to updating the same job again.

Comment 1

•
10 months ago 
The API is going away in favour of Pulse
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.