Closed Bug 1009962 Opened 8 years ago Closed 5 years ago

allow mozharness scripts to call other mozharness scripts

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: aki, Unassigned)

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3061] [mozharness])

I think the main blocker here is logging; second is /how/.

Logging: since |logging| is a global module rather than an instantiated class, we end up with duplicate log lines when we load a second instance of BaseScript.  We might be able to be smarter here.

Launching the second script: ideas currently include

a) run_command(), which will potentially contaminate the 2nd instance with the 1st instance's sys.path, venv, logging,
b) exec, which will need careful windows testing, or
c) a second script that ScriptFactory calls.
Whiteboard: [mozharness]
Assignee: nobody → aki
Component: General Automation → Mozharness
I'm probably not going to get to this any time soon.
Assignee: aki → nobody
QA Contact: catlee → aki
I think bug 1078362 would make this unnecessary.
Whiteboard: [mozharness] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3051] [mozharness]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3051] [mozharness] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3056] [mozharness]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3056] [mozharness] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3061] [mozharness]
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.