Parallelize the steps of the create_nuget CI job
Merged
ME
2mo ago+22+22+01234567890123456789-14-14-01234567890123456789
What changed
Meziantou.Analyzer.Annotationsis packed in abackgroundstep, using the parallel steps feature of GitHub Actions. It does not depend on the analyzer, so it runs whileListDotNetTypesand the pack ofMeziantou.Analyzer.Packrun sequentially.- A
wait-all: truestep waits for the background step before the artifacts are uploaded. - The
dotnet buildstep ofMeziantou.Analyzer.Packis removed, asdotnet packbuilds the projects.--no-buildis removed accordingly. - The analyzers are skipped when packing
Meziantou.Analyzer.Pack(/p:RunAnalyzers=false). The binlog shows the pack step (~2m13s) is spent inCsc(303s of cumulative compile time for the 10 analyzer/code fixer projects), and locally the analyzers account for ~70% of the compiler CPU time (17-18s vs 5-6s of CPU per project). Source generators (Meziantou.Polyfill) still run. - A new
build_with_analyzersjob buildsMeziantou.Analyzer.Pack(all Roslyn versions) with the analyzers, in parallel of the other jobs, asdotnet testinbuild_and_testdoes not run them.deploydepends on it.
Why
Speed up the create_nuget job.
Notes for reviewers
Meziantou.Analyzer.Pack.build.binlogis no longer produced: the build is now part ofMeziantou.Analyzer.Pack.pack.binlog(still uploaded by the**/*.binlogpattern).- The documentation examples found for
wait-alldon't show its value;trueis assumed. This CI run validates the syntax.