AbstractProjectGeneratorTask.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Refactored buildSrc into modules to improve feedback cycles

- Created module boundaries around different languages and slow tests

    • -313
    • +0
    ./AbstractProjectGeneratorTask.groovy
  1. … 528 more files in changeset.
Rename ProjectGeneratorTask -> TemplateProjectGeneratorTask

This provides a common base task for most of the project generators

  1. … 4 more files in changeset.
Explain how @Internal annotated inputs are tracked

Fix buildSrc/AbstractProjectGeneratorTask task properties

    • -31
    • +81
    ./AbstractProjectGeneratorTask.groovy
  1. … 3 more files in changeset.
Always generate `settings.gradle`

If not, when running a build in the performance project, Gradle may

search upwards to find the settings.gradle of the Gradle build itself

and start building buildSrc.

Finish native performance tests

Fixes gradle/gradle-native#158

  1. … 14 more files in changeset.
Fix performance test templates

Instantiate performance test projects at execution time

The detailed configuration possibilities are now unused and

instantiating these objects at configuration time just adds

unnecessary overhead.

    • -16
    • +10
    ./AbstractProjectGeneratorTask.groovy
Cleanup Java performance test projects and scenarios

- Sort tests into packages

- Add new test projects: `largeMonolithicJavaProject`,

`largeJavaMultiProject`, `mediumJavaMultiProjectWithTestNG`

- Cleanup template.gradle file

-- Remove "old Java" templates

-- Remove unused Scala and Groovy performance

test project configurations

-- Remove large enterprise performance test projects

- Simplify Java scenarios: clean assemble, first use, change test,

getting IDE models, dependency report, abi change, non-abi change

- Adjust tests to not use old test projects anymore

- Add file mutators

  1. … 96 more files in changeset.
Run GSK performance tests against small project only

Until we're sure v0.5.0 is used for all scenarios.

See gradle/gradle-script-kotlin#184

    • -4
    • +15
    ./AbstractProjectGeneratorTask.groovy
  1. … 7 more files in changeset.
Simplify performance measurements

The many measurements that we injected into the build under test were

skewing our measurements to the point of making them unreliable or

unrealistic. We now only measure end to end build time. Here's a breakdown

with the rationale for removing each other measurement:

- configuration time: can be done by having a `gradle help` scenario instead

- execution time: the user does not care whether a long build is stuck in execution or configuration

- setup/teardown: was ill-defined anyway, basically total - configuration - execution

- JIT compile time: this is nothing we can influence and thus pointless to measure

- Memory usage: Was only measured at one point in the build, which doesn't tell us anything about

any problems at any other point in the build

- GC CPU time: If this increases we'd see it in total execution time

Generally, looking at the graphs has never pointed us directly at the problem, we always need to

profile anyway. So instead of skewing our measurements with lots of profling code, we should

instead use a dedicated profiling job to measure if we actually see a regression.

Memory usage can be tested indirectly by giving each scenario a reasonable amount of memory.

If memory usage rises above that reasonable limit, we'd see execution time rise, telling us about

the regression. Generally, we do not optimize for smallest memory usage, but for fastest execution

with reasonable memory overhead.

This change also removes all JVM tweaking and wait periods which we introduced in an attempt to

make tests more predictable and stable. These tweaks have not really helped us achieve more stable

tests and have often done the opposite. They also add lots of complexity and make our tests more

unrealistic. A real users will not add all these JVM options to Gradle.

  1. … 59 more files in changeset.
Fix generation of "java software model" templates

  1. … 8 more files in changeset.
Use `buildSrc` instead of embedding classes in each subproject

The test projects all used their own copy of `CheckstyleExtension` and a custom plugin. This doesn't

reflect real projects at all. Instead, this commit changes the project layout to add a `buildSrc`

directory which contains those custom tasks/plugins.

  1. … 6 more files in changeset.
Add native project generator that uses project dependencies

    • -0
    • +236
    ./AbstractProjectGeneratorTask.groovy
  1. … 44 more files in changeset.