Closed
Bug 1161556
Opened 11 years ago
Closed 6 years ago
Simplify objdir usage in mozharness
Categories
(Release Engineering :: Applications: MozharnessCore, defect, P5)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mshal, Unassigned)
References
Details
Somewhat similar to bug 1139413, we should simplify our usage of getting an objdir in the build scripts. For example, we have at least the following in various places:
- self.query_abs_dirs()['abs_objdir']
- self.query_abs_dirs()['abs_obj_dir']
- self.objdir
- self.config['objdir']
- self._query_objdir()
Not to mention several other flavors of objdir that may or may not be redundant with these (shell_objdir, abs_analyzed_objdir, analysis-objdir). This would require some investigation to see if they can be joined with the others or not.
I think at least the first group can all be unified into a single thing in a one of the common script classes, so it is defined in one place and used the same throughout mozharness.
Updated•9 years ago
|
Priority: -- → P5
Comment 1•6 years ago
|
||
I think between simplification that has happened elsewhere, and moving logic out of mozharness into taskcluster / mach, we can mark this resolved.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•