Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Update tagging plugin to 0.56

  1. … 1 more file in changeset.
Update tagging plugin to 0.56

  1. … 1 more file in changeset.
Update tagging plugin to 0.57

  1. … 1 more file in changeset.
Update tagging plugin to 0.56

  1. … 1 more file in changeset.
Improve tagging process

Update tagging plugin and fix incorrect parameter.

  1. … 3 more files in changeset.
Improve tagging process

Update tagging plugin and fix incorrect parameter.

  1. … 3 more files in changeset.
Update tag plugin

  1. … 1 more file in changeset.
Add an opt-out to automatic target jvm setting

Builds like Gradle have "incorrect" module setups: some modules

built for Java 6 have dependencies on Java 8 modules. This, in

general, shouldn't be allowed. However in Gradle it's "fine"

because we know that when we run on Java 6, the classes which

actually need Java 8 features or dependencies are not in use.

  1. … 6 more files in changeset.
Refine GRADLE_RERUNNER (#8522)

This is the followup of https://github.com/gradle/gradle/pull/8470 : there're two issues unresolved:

- `GRADLE_RERUNNER` is configured to `Gradleception`/`compileAll`/`sanityCheck`, etc. , which makes no sense.

- We want to skip `GRADLE_RERUNNER` if there're too many failures.

This PR does:

- Extract another function `applyTestDefaults` in addition to `applyDefaults`. Functional test build and smoke test build apply `applyTestDefaults`.

- Slightly refactor `applyDefaults` function.

- Add unit tests for `applyTestDefaults`/`applyDefaults`.

- Switch to JUnit 5 for `.teamcity` project.

- Ignore the rerun if test failures are > 10.

  1. … 6 more files in changeset.
Fix cache-hit in flakiness detection performance test (#8482)

We don't want build cache hit in performance flakiness detection, however, previously the coordinator build resolves "flakiness-detection-commit" baseline to real commit id "5.3-commit-237a600", resulting in unexpected cache hit.

This PR fixes it by:

- On coordinator's side, pass "flakiness-detection-commit" as it is to worker build.

- On worker's side, worker build resolves "flakiness-detection-commit" to real commit version - this disables build cache.

Since `DetermineBaselines` is becoming more and more complex, this PR also adds a unit test for `DetermineBaselines` class.

  1. … 3 more files in changeset.
Add a build step which reruns previous failed test classes (#8470)

This closes https://github.com/gradle/gradle-private/issues/1774

We've been bitten by flaky tests for a long time. This PR adds an extra build step which reruns failed test classes again.

  1. … 3 more files in changeset.
Use 'repo.gradle.org' as repository URL

  1. … 1 more file in changeset.
Detect flaky performance test scenarios (#8367)

As part of https://github.com/gradle/gradle-private/issues/1635 , we want to detect flaky performance test with a weekly job, in order to know which scenarios are flaky.

  1. … 21 more files in changeset.
Replace :patchExternalModules with :kotlinCompilerEmbeddable

Only the kotlin-compiler-embeddable jar needs to be patched now.

Some patch actions were not needed anymore.

There's now a :kotlinCompilerEmbeddable subproject responsible for

building the patched kotlin-compiler-embeddable jar.

Only :kotlinDsl depends on it.

This greatly simplified the setup in the root project build script.

Various places required to be adjusted to account for the new setup.

The patching itself was rewritten to work in a streaming fashiong to

reduce i/o operations and disk usage. It was also moved up the

dependency tree.

All in all this should provide with a noticeable build speed up.

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -100
    • +0
    ./kotlin/org/gradle/modules/JarPatcher.kt
  1. … 8 more files in changeset.
gradlebuild.api-parameter-names-index precompiled plugin script

Signed-off-by: Paul Merlin <paul@gradle.com>

Prefer sourceSets over java.SourceSets

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 3 more files in changeset.
Fix ParameterNamesIndex task corner case issue

where types of parameter names from the same package as the observed

method were unqualified

impact was misses when querying the index for parameter names

this is an opportunistic fix as the issue doesn't affect currently

considered methods

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 1 more file in changeset.
Revert "Mark `compile` and `runtime` configurations as not resolvable"

The IDEA sync resolves the compile and runtime configurations and fails

if these cannot be resolved.

This reverts commit 15043188d7bce27d5536343cd82246ad3de9a73f.

Mark `compile` and `runtime` configurations as not resolvable

This doesn't fix anything, but allows us to capture some errors sooner,

in particular badly behaving plugins.

fix issue

  1. … 1 more file in changeset.
Add environment specific versions of test tasks

  1. … 10 more files in changeset.
Let each module jar contain an api parameter names index

for the GradleApiParameterNamesTransform to consume them

instead of regenerating it on each xform

this makes the build configuration back to normal speed

the :module:parameterNamesIndex task is cacheable but isn't that cheep

:apiMetadata:apiParameterNamesIndex is still required until the next

wrapper update

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +41
    ./kotlin/gradlebuild/api-parameter-names-index.gradle.kts
  1. … 10 more files in changeset.
Replace external modules binary dependencies by project dependencies

at this stage the build produces distributions that embed kotlin-dsl

built from subprojects instead of downloading artifacts produced by

gradle/kotlin-dsl.

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 3 more files in changeset.
Let buildSrc kotlin code satisfy comment formating ktlint rule

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 4 more files in changeset.
Disable fork point commit detection

Disable fork point commit detection

Fetch branch name from environment variable when necessary (#7947)

Previously we use JGit's branch, which might be not accurate.

Now we prefer environment variable over JGit.

  1. … 3 more files in changeset.
Build commit distribution when necessary (#7616)

This fixes https://github.com/gradle/gradle-private/issues/1640 and partially fixes https://github.com/gradle/gradle-private/issues/1632 .

In https://github.com/gradle/gradle/pull/7337 we supported running performance tests against fork point commit, now we want to make `5.1-commit-1a2b3c4d` a valid baseline version - users can specify this version in `--baselines` parameter:

- If commit baseline is set explicitly (like `5.1-commit-1a2b3c4d`), then build the corresponding commit distribution.

- Otherwise, if the current branch is not `master` or `release`, calculate the fork point commit then build the corresponding commit distribution.

This PR also publishes build scan to TeamCity build log and reuses `RemoteProject` logic and get rid of duplicate `git clone` code.

    • -0
    • +75
    ./kotlin/org/gradle/plugins/performance/DetermineBaselines.kt
  1. … 3 more files in changeset.
Add comments to IDEA import workarounds in build scripts

  1. … 1 more file in changeset.
Revert "Do not add Gradle out folders as source folders to IDEA when using Sync"

This reverts commit 5d47f9be477247f5b972cbe051e94eb88adf5fda.