Commits on Jul 25, 2016
  1. @oehme
  2. @oehme
  3. @alkemist
  4. @alkemist
  5. @alkemist
Commits on Jul 24, 2016
  1. @oehme

    Add missing templates for build scan performance tests

    The performance test generator assumes these templates to be present
    for every project. We should extract them to avoid copy-paste errors.
    oehme committed Jul 24, 2016
Commits on Jul 23, 2016
  1. @adammurdoch

    Merge branch 'release'

    adammurdoch committed Jul 24, 2016
  2. @oehme

    Fix build scan performance tests

    oehme committed Jul 23, 2016
  3. @alkemist
  4. @adammurdoch
  5. @adammurdoch
  6. @adammurdoch

    Added `@Incubating`.

    adammurdoch committed Jul 22, 2016
  7. @adammurdoch
  8. @adammurdoch


    adammurdoch committed Jul 22, 2016
  9. @adammurdoch
Commits on Jul 22, 2016
  1. @eriwen

    Merge branch 'release'

    eriwen committed Jul 22, 2016
  2. @eriwen

    Clean up NonInteractiveLaunchIntegrationTest by moving to wrapper

    project and using existing text fixtures for cleanup and verification.
    +review REVIEW-6124
    eriwen committed Jul 22, 2016
  3. @bmuschko
  4. @eriwen

    Temporarily set @LeaksFileHandles on SamplesCodeQuality test until we…

    … isolate the classloader used to execute PMD. This shall be reverted before 3.0 GA.
    eriwen committed Jul 22, 2016
  5. @bmuschko


    +review REVIEW-6123
    bmuschko committed Jul 22, 2016
  6. @bmuschko

    Merge pull request #602 from mkornipati/2.5-rup-01

    Gradle 2.5 and above ignoring excluded dependencies in genereated ivy.xml
    bmuschko committed on GitHub Jul 22, 2016
  7. @oehme
  8. @bmuschko
  9. @bmuschko

    Merge pull request #675 from ebourg/patch-2

    Compatibility fix for BouncyCastle >= 1.52
    bmuschko committed on GitHub Jul 22, 2016
  10. @oehme
  11. @oehme
  12. @oehme

    Remove unused import

    oehme committed Jul 22, 2016
  13. @oehme
  14. @oehme
  15. @oehme

    Simplify performance build scripts

    oehme committed Jul 21, 2016
  16. @oehme
  17. @oehme

    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.
    oehme committed Jul 21, 2016
Commits on Jul 21, 2016
  1. @ghale

    Change command line debug test to block when port is open

    +review REVIEW-6120
    ghale committed Jul 21, 2016
  2. @wolfs

    Mark remaining 3.0 stories as done

    wolfs committed Jul 21, 2016
  3. @lptr

    Merge branch 'release'

    lptr committed Jul 21, 2016