Use the gradle wrapper version instead of a hardcoded one #30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Modify the GitHub action config to use the gradle version used while developing, via the gradle wrapper, rather than setting a hardcoded version in the CI config, that is different than what is used while developing.
lucianbc
force-pushed
the
use-gradle-wrapper
branch
from
0368f99 to
d185662
Compare
garanj
approved these changes
Jul 12, 2024
garanj
pushed a commit
that referenced
this pull request
Jul 17, 2024
Modify the GitHub action config to use the gradle version used while developing, via the gradle wrapper, rather than setting a hardcoded version in the CI config, that is different than what is used while developing.
garanj
added a commit
that referenced
this pull request
Jul 24, 2024
* Adds support for resources.arsc parsing * Addressing issues from review * Enhance the output of the xsd-validator tool (#19) Added ✅ PASSED / ❌ FAILED to the validator tool output * Create a new workflow for the current release (#24) * Create a new workflow for the release tagged as "release" The release tagged as "release" is meant to contain the artifacts that should be used in the validation pipeline at the current moment. It differs from "latest", which is built automatically and might contain changes that we do not want to be used for now. To create a new release, the new workflow must be triggered manually with the git sha of the commit from where we want to build the artifacts. The artifacts will be available on the following permalink: ``` https://github.com/{owner}/{repo}/releases/download/{release-name}/{artifact-name} ``` * Fix workflow config * Updates validator version list in memory tool * Clarified versions with comment * Updates XSD with latest fixes (#27) * Use the gradle wrapper version instead of a hardcoded one (#30) Modify the GitHub action config to use the gradle version used while developing, via the gradle wrapper, rather than setting a hardcoded version in the CI config, that is different than what is used while developing. * Add tests for the memory footprint tool (#29) Import the existing tests for the memory footprint tool. # Conflicts: # play-validations/memory-footprint/src/main/java/com/google/wear/watchface/dfx/memory/InputPackage.java * Count analog clock hands in active Include the analog hands when used with the AnalogClock element in the active calculation. * Updates obfuscated resource handling for tests * Updates obfuscated resource handling for tests * Adds DuplicateStrategy to copy * Updates duplicate strategy * Updates implementation to use streams * Updates implementation to use streams * Fixes formatting * Remove redundant code --------- Co-authored-by: amoledwatchfaces™ <mar.cincint2@gmail.com> Co-authored-by: Lucian Boaca <lucianboaca97@gmail.com> Co-authored-by: Lucian Boaca <lucianbc@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Modify the GitHub action config to use the gradle version used while developing, via the gradle wrapper, rather than setting a hardcoded version in the CI config, that is different than what is used while developing.