You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be appreciated if to avoid such a long action time. doesn't it?
We can improve total action time by splitting the Build action into several actions.
like this:
assemble & upload aab to somewhere
spotlessCheck
lint
local unit tests & report the result
First of all, I think it is good to split assemble & upload aab to somewhere and another.
Ideally, however, lint and local unit tests should run even if spotlessCheck fails. This is because it is ideal to detect all errors at once and show them to the contributors.
The text was updated successfully, but these errors were encountered:
In the conference-app-2022, the Build action time is reached 53m eventually.
DroidKaigi/conference-app-2022#647
It would be appreciated if to avoid such a long action time. doesn't it?
We can improve total action time by splitting the Build action into several actions.
like this:
First of all, I think it is good to split assemble & upload aab to somewhere and another.
Ideally, however, lint and local unit tests should run even if spotlessCheck fails. This is because it is ideal to detect all errors at once and show them to the contributors.
The text was updated successfully, but these errors were encountered: