Closed
Bug 1312426
Opened 9 years ago
Closed 9 years ago
ATMO V2: Store history of job runs
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mdoglio, Assigned: robhudson)
References
Details
It would be useful for a job owner to keep track of job results and execution speed through time.
![]() |
||
Comment 1•9 years ago
|
||
Good idea, so each run would generate a new entry in the log and cp the job results into a separate unique folder in the bucket?
![]() |
Reporter | |
Comment 2•9 years ago
|
||
Yes, exactly.
![]() |
||
Updated•9 years ago
|
Points: --- → 2
Priority: -- → P2
![]() |
Reporter | |
Updated•9 years ago
|
![]() |
Assignee | |
Updated•9 years ago
|
Assignee: nobody → robhudson
![]() |
||
Comment 3•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•