MORPH
SIGN IN SIGN UP
bumptech / glide UNCLAIMED

An image loading and caching library for Android focused on smooth scrolling

0 0 1 Java
Normal View History Raw
Run emulator tests on travis. Also parallelizes the build a bit so that samples, the library, and the emulator tests are built and run independently.
2017-10-18 21:56:40 -07:00
#!/usr/bin/env bash
set -e
./gradlew build \
No public description PiperOrigin-RevId: 741382468
2025-03-27 20:56:08 -07:00
-x :library:test:testDebugUnitTest \
:library:test:assembleDebugUnitTest \
-x :library:testDebugUnitTest \
:library:assembleDebugUnitTest \
-x :annotation:ksp:test:testDebugUnitTest \
:annotation:ksp:test:assembleDebugUnitTest \
-x :third_party:disklrucache:testDebugUnitTest \
:third_party:disklrucache:assembleDebugUnitTest \
-x :integration:cronet:testDebugUnitTest \
:integration:cronet:assembleDebugUnitTest \
-x :integration:gifencoder:testDebugUnitTest \
:integration:gifencoder:assembleDebugUnitTest \
-x :integration:ktx:testDebugUnitTest \
:integration:ktx:assembleDebugUnitTest \
-x :integration:concurrent:testDebugUnitTest \
:integration:concurrent:assembleDebugUnitTest \
-x :integration:volley:testDebugUnitTest \
:integration:volley:assembleDebugUnitTest \
-x :integration:sqljournaldiskcache:testDebugUnitTest \
:integration:sqljournaldiskcache:assembleDebugUnitTest \
-x :third_party:gif_decoder:testDebugUnitTest \
:third_party:gif_decoder:assembleDebugUnitTest \
:samples:flickr:build \
:samples:giphy:build \
:samples:contacturi:build \
:samples:gallery:build \
:samples:imgur:build \
:samples:svg:build \
Add benchmarks for the various data types supported by Downsampler in Glide. I've added a few new types that should probably be reverted or thought through more carefully.
2021-03-17 11:25:04 -07:00
:instrumentation:assembleAndroidTest \
:benchmark:assembleAndroidTest \
Use release instead of debug variant, fixup benchmark package. From Glide's perspective these two variants are exactly the same. We don't do any different configuration for release vs debug. However, the Kotlin binary-compatibility-validator only works on the release variant and it doesn't appear to be configurable to work on a different variant. To use that plugin, we need to have a release variant. The net output here should be the same as before, just with Relase* task names instead of Debug* task names. The benchmark project changes seem to be unrelated, but I think they're actually required by some additional checks that the tools run by default on release variants but not debug variants.
2022-08-18 00:59:09 -07:00
:glide:releaseJavadoc \
Add a basic KSP Symbol Processor for Glide This library only implements support for basic configuration of Glide. Like the Java version it can detect and merge multiple LibraryGlideModules and a single AppGlideModule. The merged output (GeneratedAppGlideModule) will then be called via reflection to configure Glide when Glide is first used. Unlike the Java version this processor has no support for: 1. Extensions 2. Including or Excluding LibraryGlideModules that are added via AndroidManifest registration 3. Generated Glide, RequestOptions, RequestBuilder, and RequestManager overrides. 4. Excluding LibraryGlideModules that are added via annotations I suspect very few people use the first two missing features and so, barring major objections, those features will be only available via the Java processor and in the very long run, deprecated. Kotlin extension functions can provide the same value with less magic and complexity as Extensions. AndroidManifest registrtion has been deprecated for years. For #3 ideally we do not support these generated overrides either. Their only real purpose was to expose the functionality provided by Extensions. The one caveat is that our documentation has encouraged their use in the past. If we remove support instantly, it may complicate migration. I will support #4, but in a future change. This one is large enough already. PiperOrigin-RevId: 461943092
2022-07-19 12:14:37 -07:00
:annotation:ksp:test:test \
Add Kotlin's binary compatibility validator.
2022-08-18 01:41:05 -07:00
:integration:ktx:apiCheck \
Add integration tests for ksp library modules. I've added a new module ksp:integrationtest so that we can keep the pollution from the dependent module out of the normal library glide module tests. There's more detail in the documentation for the build.gradle file in ksp:integrationtests. This does at least make sure that if a dependent module is added, it is succesfully included by ksp. Previously the tests only tested either library modules compiled with the app glide module or library modules compiled by ksp. This new set of tests now tests library modules compiled by java. If we ever compile a module with ksp, we should add that module to these tests as well so that we have integration tests for both types of modules. For now all modules are compiled only with the java processor. In an ideal world we'd be able to just run the Java annotation processor using kotlin compile testing the same way we are with ksp. The library seems to support it. However I can't figure out a way to get the javax annotations and kotlin and android all available in a single gradle module. For now using a separate module is reasonable (if somewhat clunky) compromise.
2023-03-08 11:23:57 -08:00
:annotation:ksp:integrationtest:test \
Disable all release variants in Glide. There’s no difference whatsoever in any of our configurations between the two variants. As a result we’ve been building all of our code and running all of our tests twice, which is slow and doesn’t add any value. It’s a little weird to see that the jars we upload to maven are based on ‘debug’ variants, but that should be fine since we do nothing different for release vs debug builds. We can’t default to the release build only because AndroidStudio and other dev tools assume that the debug variant will be present.
2017-12-31 13:58:49 -08:00
--parallel
Reference in New Issue Copy Permalink