[build-tools] - Gradle build profile report with task execution breakdown by AbbanMustafa · Pull Request #3629 · expo/eas-cli

AbbanMustafa · 2026-04-24T04:04:34Z

Why

We want to give developers visibility into which Gradle tasks are consuming the most build time. This helps them and us identify optimization opportunities, especially when evaluating Gradle caching effectiveness and which modules we can improve.

How

Added --profile to the gradlew command, which tells Gradle to generate an HTML profile report. We parse this report and display the data in a build phase, broken down by module.
Added parseGradleProfile() which reads the HTML report and extracts task path, duration, and result from the Task Execution table
Added a GRADLE_BUILD_PROFILE build phase that logs a formatted table with:
- Tasks grouped by module, with individual tasks nested underneath using tree characters
- Duration, % of total time, result (executed/up-to-date/skipped/etc.), and a proportional bar chart
- Tasks under 1 second filtered out to reduce noise
- Summary line with total task count, cached/up-to-date count, and total time
Removed the previous custom trace init script and trace parsing/upload plumbing
Simplified BuildResult to return Artifacts directly since gradleProfileTasks is no longer passed up
Everything is gated behind EXPERIMENTAL_GRADLE_PROFILE=1 env var

Test Plan

Validated locally with EXPERIMENTAL_GRADLE_PROFILE=1 — profile table shows in build logs with correct task grouping and durations
Validated with EAS_GRADLE_CACHE=1 — module totals and executed tasks display correctly

byCedric · 2026-05-07T14:19:17Z

Big fan of this, after testing Android builds in Launch and seeing it's roughly 5x as slow for the default Expo template (SDK 54) - amounting for a total of 15m12s just for the gradle step

codecov · 2026-05-07T21:16:49Z

Codecov Report

❌ Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.99%. Comparing base (10c7ac6) to head (4817368).

Files with missing lines	Patch %	Lines
...ages/build-tools/src/steps/utils/android/gradle.ts	0.00%	6 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3629   +/-   ##
=======================================
  Coverage   56.99%   56.99%           
=======================================
  Files         902      902           
  Lines       38874    38874           
  Branches     8127     8127           
=======================================
  Hits        22154    22154           
  Misses      15263    15263           
  Partials     1457     1457

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

github-actions · 2026-05-07T22:26:13Z

Subscribed to pull request

File Patterns	Mentions
*/	@douglowder

Generated by CodeMention

sjchmiela · 2026-05-11T12:12:15Z


    analytics.logEvent(Event.WORKER_BUILD_SUCCESS, {});

+    if (job.platform === Platform.ANDROID && ctx.env.EXPERIMENTAL_GRADLE_PROFILE === '1') {


i've been thinking we may not need to prefix flags with EXPERIMENTAL -- until we document flags i think we can consider them experimental?

sjchmiela · 2026-05-11T12:12:30Z

+        if (profileTasks && profileTasks.length > 0) {
+          const report = formatGradleProfileReport(profileTasks);
+          for (const line of report.split('\n')) {
+            logger.info(line);


we could also logger.info(report)? or no?

bunyan escapes newlines, it will all log on one line.

what i meant is that i think we might be ok with this looking like this (package.json has newlines and prints in one… log entry)

ok if thats fine, we can do that

sjchmiela · 2026-05-11T12:14:39Z

-    env: { ...env, ...extraEnv, LC_ALL: 'C.UTF-8' },
-  });
+
+  const profileFlag = env['EXPERIMENTAL_GRADLE_PROFILE'] === '1' ? '--profile' : '';


does this impact build performance? could we add it to all builds?

it does not, yes we can and would be nice to enable by default.

sjchmiela · 2026-05-11T12:15:34Z

+  result: string;
+}
+
+export async function parseGradleProfile(


let's have a separate utility for parsing gradle profiles?

sjchmiela · 2026-05-11T12:15:50Z

+  const html = await fs.readFile(path.join(profileDir, htmlFile), 'utf8');
+
+  // Find the "Task Execution" section - it's the last <table> in the "Task Execution" tab
+  const taskExecMatch = html.match(/<h2[^>]*>\s*Task Execution\s*<\/h2>([\s\S]*?)(?:<\/div>)/i);


wouldn't it be nicer to parse the profile as an xml?

thanks I moved over to using fast-xml-parser!

sjchmiela · 2026-05-11T12:16:40Z

+  const nameWidth = Math.max(4, ...rows.map(r => r.displayName.length)) + 2;
+  const barMaxWidth = 20;
+
+  const header =


@hSATAC was formatting a table manually for xclogparsing too… i wonder if there's some kind of utility we could pull in / abstract some logic…

I agree. Will most likely prefer to keep it this way for now and then we can later agree how we would like to parse and show these in the UI

sjchmiela · 2026-05-18T19:54:18Z

+        const androidDir = path.join(ctx.getReactNativeProjectDirectory(), 'android');
+        const profileTasks = await parseGradleProfile(androidDir, logger);
+        if (profileTasks && profileTasks.length > 0) {
+          const report = formatGradleProfileReport(profileTasks);
+          logger.info(report);
+        }


shall we wrap with try-catch so if something fails here we can log the error and mark the phase as skipped? bonus points for logging the error with sentry

haven't looked it yet but i bet parseGradleProfile is probably a big try-catch, but i think maybe it's nicer to have the caller catch the error?

sjchmiela · 2026-05-18T20:03:46Z

+  const html = await fs.readFile(path.join(profileDir, htmlFile), 'utf8');
+
+  // Locate the <h2>Task Execution</h2> heading and extract its <table>
+  const headingMatch = html.match(/<h2[^>]*>\s*Task Execution\s*<\/h2>/i);


ugh i thought fast-xml-parser would give us what cheerio would do…

i'll let you decide what to do

sjchmiela · 2026-05-18T20:04:43Z

+    .pop();
+
+  if (!htmlFile) {
+    logger?.info('No Gradle profile HTML found in %s', profileDir);


so if we allowed parseGradleProfile to throw we wouldn't need to pass in logger and optionally call it. instead we could throw SystemError and catch it and log it once

sjchmiela · 2026-05-18T20:06:32Z

+
+  const tasks: GradleProfileTask[] = [];
+  for (const row of rows) {
+    const cells: any[] = row?.td;


Suggested change

const cells: any[] = row?.td;

const cells: unknown[] = row?.td;

github-actions · 2026-05-19T13:26:33Z

⏩ The changelog entry check has been skipped since the "no changelog" label is present.

AbbanMustafa added the no changelog PR that doesn't require a changelog entry label Apr 27, 2026

AbbanMustafa changed the title ~~[build] gradle parse profiler~~ [build-tools] - Gradle build profile report with task execution breakdown May 7, 2026

AbbanMustafa marked this pull request as ready for review May 7, 2026 22:25

AbbanMustafa requested a review from sjchmiela May 8, 2026 16:01

sjchmiela requested changes May 11, 2026

View reviewed changes

AbbanMustafa requested a review from sjchmiela May 18, 2026 17:48

AbbanMustafa mentioned this pull request May 18, 2026

[build-job] add GRADLE_PROFILE build phase enum #3743

Merged

sjchmiela approved these changes May 18, 2026

View reviewed changes

AbbanMustafa added 12 commits May 19, 2026 08:46

[build] gradle parse profiler

d7b4c6a

gradleProfileTasks

e38a060

individual tasks nested underneath with tree characters

e749efb

filter out whats less than 1s

ada4ce3

parseGradleProfile

7a1a38b

profile flag

057db58

enable by default

2b3b5c4

gradleProfile utils

44c1060

parse profile HTML with fast-xml-parser

0cd5b5b

parse profile HTML with fast-xml-parser

f6778ac

error handling, send to sentry

4c8a21d

sentry capture

4817368

AbbanMustafa force-pushed the mus/gradle-profiler branch from 84ebdd6 to 4817368 Compare May 19, 2026 13:26

AbbanMustafa merged commit ecf58ab into main May 19, 2026
11 checks passed

AbbanMustafa deleted the mus/gradle-profiler branch May 19, 2026 16:07


		analytics.logEvent(Event.WORKER_BUILD_SUCCESS, {});

		if (job.platform === Platform.ANDROID && ctx.env.EXPERIMENTAL_GRADLE_PROFILE === '1') {

	const cells: any[] = row?.td;
	const cells: unknown[] = row?.td;

Conversation

AbbanMustafa commented Apr 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Why

How

Test Plan

Uh oh!

byCedric commented May 7, 2026

Uh oh!

codecov Bot commented May 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

github-actions Bot commented May 7, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented May 19, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

AbbanMustafa commented Apr 24, 2026 •

edited

Loading

codecov Bot commented May 7, 2026 •

edited

Loading