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

Remove the legacy Gradle build lifecycle API #159

Merged
merged 1 commit into from
Feb 16, 2023
Merged

Conversation

jmatsu
Copy link
Contributor

@jmatsu jmatsu commented Feb 14, 2023

Related to #147 and #148

As for buildFinished, we have not used this action for a while. We can safely delete this.

finished actions has been deprecated for a while so we can remove it
@jmatsu jmatsu changed the title Remove the legacy Gradle build lifecycle API Support Configuration Cache Enabled Builds Feb 14, 2023
@jmatsu jmatsu changed the title Support Configuration Cache Enabled Builds Remove the legacy Gradle build lifecycle API Feb 14, 2023
@jmatsu jmatsu force-pushed the fix/drop_build_listener branch from 53a4505 to e3ec808 Compare February 14, 2023 06:26
@jmatsu jmatsu marked this pull request as ready for review February 14, 2023 06:59
@jmatsu jmatsu requested review from a team and satsukies and removed request for a team February 14, 2023 06:59
Copy link
Member

@satsukies satsukies left a comment

Choose a reason for hiding this comment

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

please check my comments, thanks.

@@ -116,12 +116,9 @@ abstract class UploadArtifactTask extends DefaultTask {
if (!sent && (Config.shouldOpenAppDetailAfterUpload() || response.typedResponse.application.revision == 1)) {
BrowserUtils.openBrowser "${project.deploygate.endpoint}${response.typedResponse.application.path}"
}
} catch (HttpResponseException e) {
} catch (Throwable e) {
Copy link
Member

Choose a reason for hiding this comment

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

I understand to this change behavior to send to server always.
So, I ask to reason to why aggregate to super class.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We never allow any failure when notifying lifecycle events to the server so it's better to suppress Throwable rather than specifying specific exceptions.

Copy link
Member

Choose a reason for hiding this comment

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

OK, I understand to this change is necessary 👍

@jmatsu jmatsu requested a review from satsukies February 16, 2023 05:58
Copy link
Member

@satsukies satsukies left a comment

Choose a reason for hiding this comment

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

LGTM 🙆‍♂️

@jmatsu
Copy link
Contributor Author

jmatsu commented Feb 16, 2023

Thank you so much!

@jmatsu jmatsu merged commit 0b9d447 into master Feb 16, 2023
@jmatsu jmatsu deleted the fix/drop_build_listener branch February 16, 2023 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants