performance

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Pass measurement plugin jar file to templates

- remove 'gradleTask' template variable that was used to call back from

the template

+review REVIEW-6162

    • -2
    • +1
    ./generator/tasks/ProjectGeneratorTask.groovy
  1. … 2 more files in changeset.
Add shared template arguments feature to ProjectGeneratorTask

+review REVIEW-6162

    • -1
    • +7
    ./generator/tasks/ProjectGeneratorTask.groovy
Mark sharedTemplateDirectory as optional

    • -0
    • +2
    ./generator/tasks/ProjectGeneratorTask.groovy
Remove unused relativePath feature in templates

    • -8
    • +1
    ./generator/tasks/ProjectGeneratorTask.groovy
Fix shared templates for init.gradle

    • -1
    • +1
    ./generator/tasks/ProjectGeneratorTask.groovy
Add shared templates feature

    • -0
    • +7
    ./generator/tasks/ProjectGeneratorTask.groovy
  1. … 1 more file in changeset.
Make the template directory an input directory

    • -2
    • +13
    ./generator/tasks/ProjectGeneratorTask.groovy
Merge heap-capture and build-event-timestamps templates

    • -1
    • +1
    ./generator/tasks/ProjectGeneratorTask.groovy
  1. … 3 more files in changeset.
Add configuration for measurement plugin to be used in perf test builds

    • -3
    • +11
    ./generator/tasks/ProjectGeneratorTask.groovy
  1. … 2 more files in changeset.
Split integration and performance tests

So far, performance tests were just 'integration tests in the performance project'.

This required some special handling to make sure that:

- performance tests are not run during integration test invocations

- integration tests are not run during performance test invocations

It also lead to performance tests being monolithic instead of close to the code they are testing.

This change makes performance tests a first class citizen in every project.

The common infrastructure for testing a full distribution (including daemon cleanup etc.) is now

separate from the integration tests and can be reused by other test types.

The performance tests live in their own source set called 'performanceTest'. They can define their own

dependencies and can be used independently from integration tests.

    • -0
    • +120
    ./generator/DependencyGenerator.groovy
    • -0
    • +27
    ./generator/DependencyGraph.groovy
    • -0
    • +76
    ./generator/MavenJarCreator.groovy
    • -0
    • +163
    ./generator/MavenModule.groovy
    • -0
    • +35
    ./generator/MavenPom.groovy
    • -0
    • +51
    ./generator/MavenRepository.groovy
    • -0
    • +25
    ./generator/MavenScope.groovy
    • -0
    • +80
    ./generator/RepositoryBuilder.groovy
    • -0
    • +46
    ./generator/TestProject.groovy
    • -0
    • +124
    ./generator/tasks/JvmProjectGeneratorTask.groovy
    • -0
    • +80
    ./generator/tasks/MonolithicNativeProjectGeneratorTask.groovy
    • -0
    • +44
    ./generator/tasks/NativeProjectGeneratorTask.groovy
    • -0
    • +240
    ./generator/tasks/ProjectGeneratorTask.groovy
  1. … 99 more files in changeset.