Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to run Android Studio sync with clean IDE cache #370

Merged
merged 6 commits into from
Nov 23, 2021

Conversation

asodja
Copy link
Member

@asodja asodja commented Nov 15, 2021

No description provided.

Copy link
Member

@wolfs wolfs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some comments.

gradle/wrapper/gradle-wrapper.properties Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link
Member

@wolfs wolfs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good now, I left two small comments.

@@ -10,6 +10,7 @@ public String toString() {
}
};
static final GradleBuildInvoker AndroidStudio = new GradleBuildInvoker(GradleClientSpec.AndroidStudio, GradleDaemonReuse.WarmDaemonOnly);
static final GradleBuildInvoker AndroidStudioFirstSync = new GradleBuildInvoker(GradleClientSpec.AndroidStudioFirstSync, GradleDaemonReuse.ColdDaemonOnly);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does the ColdDaemonOnly come into play here? I expect Android Studio to re-use the daemon via the tooling API, so it wouldn't be a could daemon, right?

Copy link
Member Author

@asodja asodja Nov 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Android Studio does not re-use daemon after the restart. So it always starts with the cold daemon in that case: I noticed that because we have checks in the gradle-profiler, that in case WarmDaemonOnly is set but daemon is not reused then an exception is thrown.

README.md Outdated Show resolved Hide resolved
Co-authored-by: Stefan Wolf <wolf@gradle.com>
Copy link
Member

@wolfs wolfs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@asodja asodja merged commit 3b07ba9 into master Nov 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants