flybywiresim/igniter

An intelligent task runner written in Typescript.

igniter's Issues

Allow including task graphs from subprojects using paths

• Allow including an igniter config defined in a provided path as a part of the task tree
• Execute sub graph tasks in the containing directory as cwd

Add option to ExecTask to display build output

To make debugging of build script running in the igniter context and on github actions easier I propose adding an option to the ExecTask class which allows the build to show the output of this involved scripts.

This would usually only be used temporary and the general build should not have any additional noise once it works.

Example:
new ExecTask('efb-translation', 'npm run build:efb-translation', true),

declare class GenericTask implements Task {
    key: string;
    private executor;
    private hashFolders;
    protected context: Context;
    protected errorOutput: string;
    protected showLogOutput: boolean;
    status: TaskStatus;

    /**
     * @param key The key of this generic task.
     * @param executor The TaskRunner used to run this task.
     * @param hashFolders Folders used to create caching hash.
     */
    constructor(key: string, executor: TaskRunner, showLogOutput?, hashFolders?: string[]);

...

Discord: Cdr_Maverick#6475

Thread limit flag

Why?

igniter currently runs all parallelizable tasks with an unlimited number of worker processes.

Some instrument builds in a32nx can consume up to 2GB of memory due to rollup bundling and tree-shaking.

When many (10+ in our case) of those processes exist, CI runners like GitHub Actions can OOM.

Proposed solution

Introduce a -j/--num-workers flag to limit the number of worker processes in igniter. Make sure to wait until <J workers are running to spawn a new worker.