nx core: support/add time duration logs in executors/plugins

[Hotell]

Context:

We are migrating from lage and just-scripts to nx.

just-scripts provided nice overview of duration of tasks which we used for pipeline metrics to identify perf regressions/perf improvements of tools that we use.

Example from pipeline that runs nx affected ...

just-scripts (custom)

Nx executor output (custom)

Summary:

Whilst we can implement custom execution duration logging within our custom executors/plugins it would be not consistent if we use 3rd party or nx core executors, thus it seems that best option is to have this build in within nx

[Hotell]

After Skimming through NX source, I realized nx already ships this kind of functionality in 2 modes

1. profiling mode (NX_PERF_LOGGING=true)

• nx/packages/nx/src/tasks-runner/run-command.ts

  Line 514 in 0c449b4

  lifeCycles.push(new TaskTimingsLifeCycle());

• which emits executor duration

  nx/packages/nx/src/tasks-runner/life-cycles/task-timings-life-cycle.ts

  Lines 41 to 49 in 0c449b4

  	endCommand(): void {
  	console.log('Task Execution Timings:');
  	const timings = {};
  	Object.keys(this.timings).forEach((p) => {
  	const t = this.timings[p];
  	timings[p] = t.end ? t.end - t.start : null;
  	});
  	console.log(JSON.stringify(timings, null, 2));
  	}

2. output-style=dynamic

• 

None of these solution are feasible to use for simple task execution measurement logging :

1. enabling profiling mode on every CI run would provide unnecessary churn to CI logs
2. output=dynamic doesn't work on CI

Proposed Solution:

IMO the best option would be to incorporate output=dynamic logs ((number s)) within output=static logs.

Which brings us to following kinda related issue #15570

WDYT?