opensourcemirror
/
fdroid-client
mirror of https://gitlab.com/fdroid/fdroidclient.git
1
0
Fork 0
Code Issues Releases Wiki Activity
fdroid-client/.gitlab-ci.yml

97 lines
3.2 KiB
YAML
Raw Normal View History

Bump build-tools and docker image version The latter is simply to include the newer version.
2016-09-10 12:02:12 +02:00
image: mvdan/fdroid-ci:client-20160909
CI: Use our docker image
2016-02-29 15:15:02 +01:00
gitlab-ci: cache downloaded things between builds This stores the Android SDK tarball and gradle caches between builds to speed things up. Since the unpacked SDK gets unpacked very time, updating the version is just a matter of changing the variable. Since only the gradle caches are stored, i.e. the jars and gradle binaries, updates there will only add more files to the cache.
2016-02-24 20:31:42 +01:00
cache:
paths:
- .gradle/wrapper
- .gradle/caches
CI: Rename build task to test To clarify that it is running the unit tests too.
2016-05-16 12:57:49 +02:00
test:
First try at a gitlab CI script
2015-08-27 05:28:38 +02:00
script:
gitlab-ci: cache downloaded things between builds This stores the Android SDK tarball and gradle caches between builds to speed things up. Since the unpacked SDK gets unpacked very time, updating the version is just a matter of changing the variable. Since only the gradle caches are stored, i.e. the jars and gradle binaries, updates there will only add more files to the cache.
2016-02-24 20:31:42 +01:00
- export GRADLE_USER_HOME=$PWD/.gradle
CI: Don't use the confusing "build" gradle task Be more explicit about what we're running. This also means that we wont run the "read log here" stuff if the build failed, which didn't make any sense. That should only be run if the unit tests fail.
2016-05-12 16:41:46 +02:00
- ./gradlew assemble -PdisablePreDex
gitlab-ci: enable lint and run tools scripts in parallel * splitting out the tools script allows less things to happen on the main job, and runs the tools script in parallel, which should speed things up. * `gradle check` also runs lint, and anything else we might add to that meta-target. * `gradle build` also runs tests, `gradle assemble` does not
2016-02-24 22:59:01 +01:00
# always report on lint errors to the build log
move main project files into standard gradle/Android Studio layout This makes it a lot easier to setup all the testing stuff. Mostly, I'm tired of fighting Android Studio's fragility, so I want to remove as much non-standardness as possible in the hopes of improving that situation. closes #534 https://gitlab.com/fdroid/fdroidclient/issues/534
2016-03-28 12:12:37 +02:00
- sed -i -e 's,textReport .*,textReport true,' app/build.gradle
CI: Don't use the confusing "build" gradle task Be more explicit about what we're running. This also means that we wont run the "read log here" stuff if the build failed, which didn't make any sense. That should only be run if the unit tests fail.
2016-05-12 16:41:46 +02:00
- ./gradlew lint -PdisablePreDex
- ./gradlew test -PdisablePreDex || {
gitlab-ci: upload full build logs to clbin.com I find that the logs dumped into the gitlab-ci screens are generally unreadable, so here, only the errors are dumped into the build log, then the rest are uploaded to clbin, a paste bin, where the whole text can be viewed and downloaded in a clean, raw format.
2016-04-04 21:13:44 +02:00
for log in app/build/reports/*ests/*/*ml; do
gitlab-ci: add missing semi-colon in failure script It was echoing 'cat "$log" instead of cat'ing the log.
2016-05-03 11:59:55 +02:00
echo "read $log here:";
gitlab-ci: upload full build logs to clbin.com I find that the logs dumped into the gitlab-ci screens are generally unreadable, so here, only the errors are dumped into the build log, then the rest are uploaded to clbin, a paste bin, where the whole text can be viewed and downloaded in a clean, raw format.
2016-04-04 21:13:44 +02:00
cat "$log" | curl --silent -F 'clbin=<-' https://clbin.com;
done;
exit 1;
}
CI: Remove lock file after every task I tried using after_script, but it seems to not be supported on gitlab.com's public runners.
2016-05-12 16:18:24 +02:00
# this file changes every time but should not be cached
- rm -f $GRADLE_USER_HOME/caches/modules-2/modules-2.lock
gitlab-ci: another gradle bit to delete for good caching recommended here, seems like it can't hurt: https://docs.travis-ci.com/user/languages/java/#Caching
2016-06-21 17:02:40 +02:00
- rm -fr $GRADLE_USER_HOME/caches/*/plugin-resolution/
CI: Split build and connectedCheck tasks Advantages: * Failing unit tests don't keep the android tests from running * CI should be overall faster as the tasks get run in parallel and the former `gradle` task was the longest by far This will later simplify the multiplexing of the android tests onto multiple emulators.
2016-05-12 16:18:41 +02:00
CI: Add android-10 connectedCheck task GitLab doesn't currently support any kind of build or env matrix, so we have to duplicate this code. This is due to change in upcoming releases, at which point I'll fix this.
2016-05-16 12:42:58 +02:00
connected10:
variables:
AVD_SDK: "10"
script:
- export GRADLE_USER_HOME=$PWD/.gradle
- emulator64-arm -avd fcl-test-$AVD_SDK -no-skin -no-audio -no-window &
- ./tools/wait-for-emulator
- adb shell input keyevent 82 &
- export EXITVALUE=0
- ./gradlew connectedCheck -PdisablePreDex || {
adb -e logcat -d '*:E';
echo "get the full logcat here:";
adb -e logcat -d | curl --silent -F 'clbin=<-' https://clbin.com;
export EXITVALUE=1;
}
- for log in app/build/reports/*ests/*/*ml
app/build/outputs/*results*/connected/*.xml; do
echo "read $log here:";
cat "$log" | curl --silent -F 'clbin=<-' https://clbin.com;
done
# this file changes every time but should not be cached
- rm -f $GRADLE_USER_HOME/caches/modules-2/modules-2.lock
- exit $EXITVALUE
gitlab-ci: reduce connected10 from error to warning connected10 is still flaky since the emulator crashes a lot. Marking it for "allow_failure" will still show a warning, but it won't fail the build.
2016-09-27 13:08:30 +02:00
allow_failure: true
CI: Add android-10 connectedCheck task GitLab doesn't currently support any kind of build or env matrix, so we have to duplicate this code. This is due to change in upcoming releases, at which point I'll fix this.
2016-05-16 12:42:58 +02:00
CI: switch to android-24 emulator
2016-07-10 02:32:48 +02:00
connected24:
CI: Move variables to connectedCheck AVD_SDK is only used there. And MALLOC_ARENA_MAX was added when the android-17 emulator was added, so it should stay there.
2016-05-12 16:23:30 +02:00
variables:
CI: switch to android-24 emulator
2016-07-10 02:32:48 +02:00
AVD_SDK: "24"
CI: Split build and connectedCheck tasks Advantages: * Failing unit tests don't keep the android tests from running * CI should be overall faster as the tasks get run in parallel and the former `gradle` task was the longest by far This will later simplify the multiplexing of the android tests onto multiple emulators.
2016-05-12 16:18:41 +02:00
script:
- export GRADLE_USER_HOME=$PWD/.gradle
CI: switch to android-24 emulator
2016-07-10 02:32:48 +02:00
- emulator64-x86 -avd fcl-test-$AVD_SDK -no-skin -no-audio -no-window &
Move wait-for-emulator out of F-Droid subdir It doesn't specifically apply only to the client.
2015-10-02 04:50:37 +02:00
- ./tools/wait-for-emulator
gitlab-ci: run `adb shell input keyevent 82` in the background This is the common pattern I've seen in travis-ci builds. It should speed things up a little bit since the adb connection process will happen in parallel with waiting for the screen lock to be dismissed.
2016-04-05 00:21:45 +02:00
- adb shell input keyevent 82 &
gitlab-ci: upload full build logs to clbin.com I find that the logs dumped into the gitlab-ci screens are generally unreadable, so here, only the errors are dumped into the build log, then the rest are uploaded to clbin, a paste bin, where the whole text can be viewed and downloaded in a clean, raw format.
2016-04-04 21:13:44 +02:00
- export EXITVALUE=0
CI: No more need to set ADB_INSTALL_TIMEOUT The default was bumped in the Android plugin version 2.0.0, so we are safe now.
2016-05-12 16:32:03 +02:00
- ./gradlew connectedCheck -PdisablePreDex || {
gitlab-ci: upload full build logs to clbin.com I find that the logs dumped into the gitlab-ci screens are generally unreadable, so here, only the errors are dumped into the build log, then the rest are uploaded to clbin, a paste bin, where the whole text can be viewed and downloaded in a clean, raw format.
2016-04-04 21:13:44 +02:00
adb -e logcat -d '*:E';
echo "get the full logcat here:";
adb -e logcat -d | curl --silent -F 'clbin=<-' https://clbin.com;
export EXITVALUE=1;
}
- for log in app/build/reports/*ests/*/*ml
app/build/outputs/*results*/connected/*.xml; do
echo "read $log here:";
cat "$log" | curl --silent -F 'clbin=<-' https://clbin.com;
done
gitlab-ci: improve caching of gradle stuff
2016-04-11 22:06:01 +02:00
# this file changes every time but should not be cached
- rm -f $GRADLE_USER_HOME/caches/modules-2/modules-2.lock
gitlab-ci: another gradle bit to delete for good caching recommended here, seems like it can't hurt: https://docs.travis-ci.com/user/languages/java/#Caching
2016-06-21 17:02:40 +02:00
- rm -fr $GRADLE_USER_HOME/caches/*/plugin-resolution/
gitlab-ci: upload full build logs to clbin.com I find that the logs dumped into the gitlab-ci screens are generally unreadable, so here, only the errors are dumped into the build log, then the rest are uploaded to clbin, a paste bin, where the whole text can be viewed and downloaded in a clean, raw format.
2016-04-04 21:13:44 +02:00
- exit $EXITVALUE
gitlab-ci: enable lint and run tools scripts in parallel * splitting out the tools script allows less things to happen on the main job, and runs the tools script in parallel, which should speed things up. * `gradle check` also runs lint, and anything else we might add to that meta-target. * `gradle build` also runs tests, `gradle assemble` does not
2016-02-24 22:59:01 +01:00
pmd:
script:
- export GRADLE_USER_HOME=$PWD/.gradle
improve build server performance by allowing disabling of pre-dexing It seems that Google is finally paying some attention to CI builds with the emulator, they issued a recommendation: http://tools.android.com/tech-docs/new-build-system/tips#TOC-Improving-Build-Server-performance
2016-04-05 00:16:00 +02:00
- ./gradlew pmd -PdisablePreDex
CI: Remove lock file after every task I tried using after_script, but it seems to not be supported on gitlab.com's public runners.
2016-05-12 16:18:24 +02:00
# this file changes every time but should not be cached
- rm -f $GRADLE_USER_HOME/caches/modules-2/modules-2.lock
gitlab-ci: another gradle bit to delete for good caching recommended here, seems like it can't hurt: https://docs.travis-ci.com/user/languages/java/#Caching
2016-06-21 17:02:40 +02:00
- rm -fr $GRADLE_USER_HOME/caches/*/plugin-resolution/
gitlab-ci: enable lint and run tools scripts in parallel * splitting out the tools script allows less things to happen on the main job, and runs the tools script in parallel, which should speed things up. * `gradle check` also runs lint, and anything else we might add to that meta-target. * `gradle build` also runs tests, `gradle assemble` does not
2016-02-24 22:59:01 +01:00
checkstyle:
script:
- export GRADLE_USER_HOME=$PWD/.gradle
improve build server performance by allowing disabling of pre-dexing It seems that Google is finally paying some attention to CI builds with the emulator, they issued a recommendation: http://tools.android.com/tech-docs/new-build-system/tips#TOC-Improving-Build-Server-performance
2016-04-05 00:16:00 +02:00
- ./gradlew checkstyle -PdisablePreDex
CI: Remove lock file after every task I tried using after_script, but it seems to not be supported on gitlab.com's public runners.
2016-05-12 16:18:24 +02:00
# this file changes every time but should not be cached
- rm -f $GRADLE_USER_HOME/caches/modules-2/modules-2.lock
gitlab-ci: another gradle bit to delete for good caching recommended here, seems like it can't hurt: https://docs.travis-ci.com/user/languages/java/#Caching
2016-06-21 17:02:40 +02:00
- rm -fr $GRADLE_USER_HOME/caches/*/plugin-resolution/
gitlab-ci: enable lint and run tools scripts in parallel * splitting out the tools script allows less things to happen on the main job, and runs the tools script in parallel, which should speed things up. * `gradle check` also runs lint, and anything else we might add to that meta-target. * `gradle build` also runs tests, `gradle assemble` does not
2016-02-24 22:59:01 +01:00
tools:
script:
move main project files into standard gradle/Android Studio layout This makes it a lot easier to setup all the testing stuff. Mostly, I'm tired of fighting Android Studio's fragility, so I want to remove as much non-standardness as possible in the hopes of improving that situation. closes #534 https://gitlab.com/fdroid/fdroidclient/issues/534
2016-03-28 12:12:37 +02:00
- cd app
gitlab-ci: enable lint and run tools scripts in parallel * splitting out the tools script allows less things to happen on the main job, and runs the tools script in parallel, which should speed things up. * `gradle check` also runs lint, and anything else we might add to that meta-target. * `gradle build` also runs tests, `gradle assemble` does not
2016-02-24 22:59:01 +01:00
- ./tools/langs-list-check.py
- ./tools/check-string-format.py