Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Refine build configurations on EC2 agents (#12252)

Refine build configurations on EC2 agents

  1. … 4 more files in changeset.
Collect IDE sync times through build scans

  1. … 2 more files in changeset.
Capture VFS retention enabling in build scans

So we have better usage data

Combine and rewrite all documentation generation

  1. … 276 more files in changeset.
Integrate with Gradle Enterprise plugin 3.0 (#11041)

  1. … 52 more files in changeset.
Rerun distributed performance test in RERUNNER step (#8801)

After the improvement of automatically rerunning and tagging, we want to manage performance test in the same way:

- Only run each performance test scenario once.

- If it fails, `GRADLE_RERUNNER` will kick in and rerun the failed scenario. The good thing is that it might be scheduled to another build agent, which mitigates the effect of bad agent.

This PR does:

- Remove all `Retry` from performance tests.

- Add `GRADLE_RERUNNER` to performance tests and refactor some code.

- Add tests for `PerformanceTest`.

- Since `GRADLE_RERUNNER` depends on reading of test binary result, write binary test result file in `RerunableDistributedPerformanceTest`.

  1. … 23 more files in changeset.
Remove unused custom values for build cache

We now get enough information out of the box about buildSrc task, we

don't need to add the custom values.

Add a build step which reruns previous failed test classes (#8470)

This closes

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.
Fix CACHE_MISSes for asciidoctor tasks (#8469)

I noticed several `CACHE_MISS`es caused by asciidoctor tasks. There're two issues:

- The GE performance tests are running `CacheableAsciidoctorTask` without seed builds.

- The promotion builds' build cache is disabled so they can't fetch data from cache.

This PR fixes these two issues.

Add expected cache-miss criteria (#8390)

We observed some CACHE_MISSes and this PR fixes them

Make AsciidoctorTask cacheable again (#8148)

This fixes

This PR does:

- Re-enables `CacheableAsciidoctorTask`

- Updates everything to the latest version.

- Fixes several broken cacheability issues.

- Tag the build `CACHE_MISS` upon unexpected cache-miss.

  1. … 6 more files in changeset.
Use build type id to identify compileAll task

Rename build type id to match current TC build

Use a flag to avoid duplicate CACHE_MISS tag (#8081)

This fixes

Previously we didn't check if a build is already tagged `CACHE_MISS` before tagging. This PR adds an `AtomicBoolean` as a flag to avoid duplicate tags.

Support for building Gradle on Jenkins

This allows for building Gradle on Jenkins with useful build scan tags.

  1. … 1 more file in changeset.
Don't publish CACHE_MISS tag in buildScanPluginPerformanceTest (#8029)

Because it doesn't depend on compileAll task.

Tag CACHE_MISS upon unexpected cache miss (#7869)

This is the first-step implementation of

Previously sometimes we see unexpected cache misses in the build, which we want to monitor. This PR marks all non-skipped `AbstractCompile` and `ClasspathManifest` tasks as `CACHE_MISS` if current build is not `compileAll`, so that this build can be searched in build scan later.

  1. … 1 more file in changeset.
Add build scan tag when executed from IDEA

The `BuildScanPlugin` now tries to detect if the build has been

executed from IDEA. It also tries to add the version as a custom


It seems like different versions of IDEA set different properties.

For example, I didn't see `idea.registered` and `` at

the same time, yet.

Remove links from build scans created on Travis

- Remove report links (only works on TC)

- Remove links to `` GE instance for current commit

  1. … 1 more file in changeset.
Fix Kotlin compiler warning

`envValue` is now known to be non-null at that point.

Merge pull request #7457 from marcphilipp/marc/travis

Introduce Travis build for contributor PRs

Run performance test against fork point commit (#7337)

This closes

Basically, the idea is, we should run feature branch performance tests against the distribution which is built from the "fork point commit". This can reduce the effects of performance regression which is not introduced by the feature branch.

Two tasks are added into the build and depended by performance task:

- `determineForkPoint`, run `git` command to determine the fork point commit. It's done during the execution phase, then it sets the commit for `buildForkPointDistribution` task.

- `buildForkPointDistribution`, try to build a distribution from the fork point commit.

`buildForkPointDistribution` is cachable so it only needs to run once. Its input is the fork point commit, the output is two files: a binary distribution and a tooling api jar. The generated binary distribution is used to run individual worker tests.

  1. … 12 more files in changeset.
Add support for Travis

Fix BuildScanPlugin.system() hanging on Windows

Add search links to build scan (#6913)

Now there is a link to search scans for

- the same commit id

- the compile all build for the commit id

- the same build type

Reuse `Gradle.serviceOf` extension

Build scan plugin should not fail when build fails

Build scan plugin should not fail when build fails

Add classloader details only once per task to build scan

We have been adding duplicate information about the classloader details

of selected tasks (times the number of subprojects).

Let's not do that.

Polish `BuildScanPlugin`

- Suppress unused warning on plugin class

- Move auxiliary function to after its uses

- Shorten long expression with duplicate sub-expression via ` { }`

- Deduplicate `buildScan` receiver by

- Nesting `background` expressions under single `buildScan` block

- Removing nested `buildScan` blocks

- Simplify `setCommitId` by changing receiver to `BuildScanExtension`