Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove Gradle inception performance test. This test doesn't seem to cover anything that isn't already covered by another performance scenario, and adds cost to using new features in the Gradle build.

  1. … 1 more file in changeset.
Remove Gradle inception performance test. This test doesn't seem to cover anything that isn't already covered by another performance scenario, and adds cost to using new features in the Gradle build.

  1. … 1 more file in changeset.
Remove Gradle inception performance test. This test doesn't seem to cover anything that isn't already covered by another performance scenario, and adds cost to using new features in the Gradle build.

  1. … 1 more file in changeset.
Move daemon process cleanup before and after functional tests to a build service.

    • -1
    • +1
    ./testing/DistributedPerformanceTest.groovy
  1. … 14 more files in changeset.
Move daemon process cleanup before and after functional tests to a build service.

    • -1
    • +1
    ./testing/DistributedPerformanceTest.groovy
  1. … 12 more files in changeset.
Move daemon process cleanup before and after functional tests to a build service.

    • -1
    • +1
    ./testing/DistributedPerformanceTest.groovy
  1. … 14 more files in changeset.
Move daemon process cleanup before and after functional tests to a build service.

    • -1
    • +1
    ./testing/DistributedPerformanceTest.groovy
  1. … 12 more files in changeset.
Print error message when encountering issues

    • -3
    • +3
    ./testing/DistributedPerformanceTest.groovy
Use directory in root project to build commit distribution

So directories are short enough for Windows m)

  1. … 1 more file in changeset.
Use directory in root project to build commit distribution

So directories are short enough for Windows m)

  1. … 1 more file in changeset.
Use directory in root project to build commit distribution

So directories are short enough for Windows m)

  1. … 1 more file in changeset.
Use directory in root project to build commit distribution

So directories are short enough for Windows m)

  1. … 1 more file in changeset.
Pin all remote projects to exact refs, don't use branches

Pinning to branches means the build is not fully reproducible, as changes in the remote repo can alter the outcome of this build.

  1. … 3 more files in changeset.
Use dedicated user with token-based authentication to execute… (#11044)

Replace password-based authentication with token in distributed performance tests

    • -6
    • +3
    ./testing/DistributedPerformanceTest.groovy
  1. … 7 more files in changeset.
Use dedicated user with token-based authentication to execute… (#11044)

Replace password-based authentication with token in distributed performance tests

    • -6
    • +3
    ./testing/DistributedPerformanceTest.groovy
  1. … 7 more files in changeset.
Use dedicated user with token-based authentication to execute… (#11044)

Replace password-based authentication with token in distributed performance tests

    • -6
    • +3
    ./testing/DistributedPerformanceTest.groovy
  1. … 7 more files in changeset.
Replace password-based authentication with token in distributed performance tests

    • -6
    • +3
    ./testing/DistributedPerformanceTest.groovy
  1. … 8 more files in changeset.
Replace TeamCityRestBot

    • -6
    • +3
    ./testing/DistributedPerformanceTest.groovy
  1. … 8 more files in changeset.
Revert "Make DistributedPerformanceTest non-abstract"

This reverts commit c7b91fc418865d3660723eb42ea5e749b11651e0.

    • -7
    • +3
    ./testing/DistributedPerformanceTest.groovy
Make DistributedPerformanceTest non-abstract

Seems like the Gradleception build fails when it is abstract...

    • -3
    • +7
    ./testing/DistributedPerformanceTest.groovy
Remove one level from the JUnitXmlEvents

WorkerSuites seems to be unnecessary.

    • -5
    • +3
    ./testing/JUnitXmlTestEventsGenerator.groovy
Remove one level from the JUnitXmlEvents

WorkerSuites seems to be unnecessary.

    • -5
    • +3
    ./testing/JUnitXmlTestEventsGenerator.groovy
Remove unused properties

    • -18
    • +0
    ./testing/DistributedPerformanceTest.groovy
Remove unused properties

    • -18
    • +0
    ./testing/DistributedPerformanceTest.groovy
Add Javadoc

    • -0
    • +18
    ./testing/DistributedPerformanceTest.groovy
    • -0
    • +14
    ./testing/PerformanceScenarioRerunStrategy.java
    • -0
    • +8
    ./testing/RetryFailedRerunStrategy.java
Add Javadoc for new methods

    • -0
    • +18
    ./testing/DistributedPerformanceTest.groovy
    • -0
    • +14
    ./testing/PerformanceScenarioRerunStrategy.java
    • -0
    • +8
    ./testing/RetryFailedRerunStrategy.java
Add Javadoc

    • -0
    • +18
    ./testing/DistributedPerformanceTest.groovy
    • -0
    • +14
    ./testing/PerformanceScenarioRerunStrategy.java
    • -0
    • +8
    ./testing/RetryFailedRerunStrategy.java
Move rerun strategy to property

and add some DSL to configure it.

    • -6
    • +18
    ./testing/DistributedPerformanceTest.groovy
    • -1
    • +10
    ./testing/PerformanceScenarioRerunStrategy.java
    • -7
    • +7
    ./testing/RetryFailedRerunStrategy.java
  1. … 1 more file in changeset.
Move rerun strategy to property

and add some DSL to configure it.

    • -6
    • +18
    ./testing/DistributedPerformanceTest.groovy
    • -1
    • +10
    ./testing/PerformanceScenarioRerunStrategy.java
    • -7
    • +7
    ./testing/RetryFailedRerunStrategy.java
  1. … 1 more file in changeset.
The reporter checks for errors

so don't, check in the performance task as well. This worked before

since only the retry task needed to have the "right" outcome.

    • -11
    • +0
    ./testing/DistributedPerformanceTest.groovy