Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Run distributed performance test with retry

    • -4
    • +4
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
    • -4
    • +6
    /.teamcity/common/performance-test-extensions.kt
Fix failed TC Kotlin DSL test

Update tagging plugin (#8800)

This PR applies latest tagging plugin (which runs tagging in `GRADLE_RERUN` step) and removes `TAG_BUILD` steps in configurations.

Remove flakiness test code

Update to 0.62

Update released version to latest snapshot

Update library versions in build init to latest for 5.5

Update version to 5.5

Clean release notes and welcome message for 5.5

    • -7
    • +1
    /subprojects/docs/src/docs/release/notes.md
Update to 0.61

Fix issues in plugin 0.60

Publish 5.3-20190320013427+0000

Test flaky handling

Test flaky handling

Use common methods in AdHoc performance job

    • -1
    • +0
    /.teamcity/common/performance-test-extensions.kt
Use common methods in AdHoc performance job

Merge pull request #8715 from gradle/wolfs/xforms/improve-scheduler-performance

Improve performance of scheduler in the presence of many nodes

Fix null handling of DirectoryProperty/RegularFileProperty.set(File)

Previously, we failed in a strange way if you explicitly called set(File) with a null.

set(Directory) or set(RegularFile) were OK.

Fix null handling of DirectoryProperty/RegularFileProperty.set(File)

Previously, we failed in a strange way if you explicitly called set(File) with a null.

set(Directory) or set(RegularFile) were OK.

Fix null handling of DirectoryProperty/RegularFileProperty.set(File)

Previously, we failed in a strange way if you explicitly called set(File) with a null.

set(Directory) or set(RegularFile) were OK.

Move new method to a better place

Extract common code for AdHoc Coordinator Job

    • -0
    • +55
    /.teamcity/common/performance-test-extensions.kt
Extract common code for AdHoc Coordinator Job

    • -0
    • +55
    /.teamcity/common/performance-test-extensions.kt
Merge pull request #8805 from gradle/wolfs/cacheable-minify-transform

Enable caching for Minify transform

Add test for strange finalizer behaviour

When there is a finalizer with some other tasks which needs to run after

the finalizer, then depending on how many executers there are, the

tasks may run in different order.

Situation:

dependency -> finalized -finalizedBy-> finalizer -mustRunBefore

-> mustRunAfter

mustRunAfter can run right at the beginning, since its dependencies are

completed. Though when the finalized task finished, causing the

finalizer task to must run, mustRunAfter needs to wait until finalizer

finishes to start executing.

Merge branch 'master' into bamboo/release/polish-type-safe-accessors

Merge branch 'master' into bamboo/master/build/take-advantage-of-type-safe-accessors

Check logger type for decorating

TeamCity change in 'Gradle / Util' project: Versioned settings configuration updated

    • -0
    • +29
    /.teamcity/Gradle_Util/Project.kt
    • -18
    • +0
    /.teamcity/Gradle_Util/project-config.xml
    • -0
    • +35
    /.teamcity/Gradle_Util/settings.kts
    • -0
    • +15
    /.teamcity/Gradle_Util_Performance/Project.kt
Some cleanup