Analyze how Treeherder retriggers selected jobs
Categories
(Tree Management :: Perfherder, task, P3)
Tracking
(Not tracked)
People
(Reporter: igoldan, Unassigned)
References
(Blocks 1 open bug)
Details
Provide here an overview of this mechanism, so we now how to integrate it in Perfherder as well.
Reporter | ||
Updated•4 months ago
|
Reporter | ||
Comment 1•4 months ago
•
|
||
Looks like JobModel.retrigger(jobs, repoName, notify, times)
is the main API we have to use.
Basically, we only need to know the perf jobs we want to retrigger & their repository.
This findings should suffice reusing this functionality on FE.
One weird thing I see: it appears repoName
is not used inside this static method. :camd why is that? Could I just remove this parameter from this function signature?
Comment 2•4 months ago
|
||
Yeah, it's a bit of a vestigial artifact. We don't need it anymore, but some of the endpoints require it. I have been trying to remove the need for it as we go. And, yes, you're right. That call doesn't even use it now. :) So please feel free to remove it from retrigger as well as the other functions where it's no longer used.
I should have removed that before, but somehow forgot to do so...
Updated•Last month
|
Reporter | ||
Updated•Last month
|
Description
•