Remove baseline profiles that are committed to version control
Categories
(Fenix :: Performance, task, P1)
Tracking
(Not tracked)
People
(Reporter: jonalmeida, Assigned: titouan)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][group4] [fxdroid])
As part of bug 1807350, we generated profiles and committed them to the codebase to avoid blockers within infrastructure tooling during the prototype phase.
Once the work to automate and package the baseline profiles for each build is done, we should remove the existing profiles and add an ignore that stops anyone from committing them in the future.
|
Assignee | |
Updated•4 months ago
|
|
||
Updated•4 months ago
|
|
|
Assignee | |
Comment 1•4 months ago
|
||
The generated profile was actually removed from the tree in D221635.
As the profile is now generated automatically as part as the release pipeline, I guess we don't need to add an ignore that avoids commiting new profiles in the future? What do you think?
|
|
Assignee | |
Comment 2•4 months ago
|
||
The bug was marked as fixed by mistake. I'll reopen it and only close it if you confirm that we don't need to add an ignore for the baseline profiles.
|
Reporter | |
Comment 3•4 months ago
|
||
(In reply to Titouan Thibaud [:titouan] from comment #1)
The generated profile was actually removed from the tree in D221635.
As the profile is now generated automatically as part as the release pipeline, I guess we don't need to add an ignore that avoids commiting new profiles in the future? What do you think?
Oh cool - happy to see it was removed. Yeah, I think it's fine to skip the an ignore entry if this is part of our build pipeline now. We can always re-open if we change our mind. Thanks!
Description
•