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

84 lines
2.9 KiB
YAML
Raw Normal View History

gitlab-ci: don't fail build if clbin fails clbin is just for making the logs easy to read, if it fails, the build should not be marked as failed, especially since the logs are probably not needed if the rest of the job succeeded.
2017-09-06 16:59:04 +02:00
image: registry.gitlab.com/fdroid/ci-images-client:latest
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
gitlab-ci: use before and after script for reused chunks It also reduces redundancy by using before_script and after_script blocks.
2016-09-27 16:19:45 +02:00
before_script:
- export GRADLE_USER_HOME=$PWD/.gradle
gitlab-ci: ensure compile platform is installed Avoid broken builds when fdroidclient gets out of sync with ci-images/client. `emulator -no-skin` no longer does anything, but give a warning.
2017-03-17 12:29:45 +01:00
- export ANDROID_COMPILE_SDK=`sed -n 's,.*compileSdkVersion\s*\([0-9][0-9]*\).*,\1,p' app/build.gradle`
- echo y | android --silent update sdk --no-ui --filter android-${ANDROID_COMPILE_SDK}
gitlab-ci: use before and after script for reused chunks It also reduces redundancy by using before_script and after_script blocks.
2016-09-27 16:19:45 +02:00
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: make blank/unused translate output clearer This test now shows the actual blank/unused translations, so it should be a lot clearer why this test is failing. !519
2017-05-19 23:35:11 +02:00
- export EXITVALUE=0
move all translation scripts to tools/ I think we should just move all the scripts to tools/, app/tools is confusing, not very visible, and non-standard.
2017-05-10 11:01:50 +02:00
- ./tools/check-format-strings.py
gitlab-ci: fail if translation strings need corrections Since we have all these lovely scripts for cleaning up the translations, gitlab-ci is a handy way to enforce that they get used. Since weblate merges happen via merge requests, this will work nicely now. I can't think of any false positives that will arise, but we shall find out!
2017-05-10 11:51:26 +02:00
- ./tools/remove-unused-and-blank-translations.py
gitlab-ci: make blank/unused translate output clearer This test now shows the actual blank/unused translations, so it should be a lot clearer why this test is failing. !519
2017-05-19 23:35:11 +02:00
- echo "These are unused or blank translations that should be removed:"
- git --no-pager diff --exit-code || export EXITVALUE=1
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
gitlab-ci: put all the static tests into test job gitlab-ci used to run all of our jobs in parallel, now it mostly seems to run them sequentially. So splitting up the various parts of the CI suite into separate jobs mostly slows things down. This combines the static tests into one job (lint, pmd, checkstyle, tools) with the JVM tests aka Robolectric. That makes three jobs from the previous six.
2017-02-24 22:20:02 +01:00
- ./gradlew pmd -PdisablePreDex
- ./gradlew checkstyle -PdisablePreDex
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 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: don't fail build if clbin fails clbin is just for making the logs easy to read, if it fails, the build should not be marked as failed, especially since the logs are probably not needed if the rest of the job succeeded.
2017-09-06 16:59:04 +02:00
(cat "$log" | curl --silent -F 'clbin=<-' https://clbin.com) || true;
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
done;
gitlab-ci: make blank/unused translate output clearer This test now shows the actual blank/unused translations, so it should be a lot clearer why this test is failing. !519
2017-05-19 23:35:11 +02:00
export EXITVALUE=1;
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
}
gitlab-ci: make blank/unused translate output clearer This test now shows the actual blank/unused translations, so it should be a lot clearer why this test is failing. !519
2017-05-19 23:35:11 +02:00
- exit $EXITVALUE
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:
gitlab-ci: build before starting emulator to speed things up The emulator will grab a bunch of RAM, so run assemble before connectedCheck so that the app is mostly built before starting the emulator.
2017-03-17 12:42:59 +01:00
- ./gradlew assembleDebug -PdisablePreDex
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
- 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:";
gitlab-ci: don't fail build if clbin fails clbin is just for making the logs easy to read, if it fails, the build should not be marked as failed, especially since the logs are probably not needed if the rest of the job succeeded.
2017-09-06 16:59:04 +02:00
(adb -e logcat -d | curl --silent -F 'clbin=<-' https://clbin.com) || 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
export EXITVALUE=1;
}
- for log in app/build/reports/*ests/*/*ml
app/build/outputs/*results*/connected/*.xml; do
echo "read $log here:";
gitlab-ci: don't fail build if clbin fails clbin is just for making the logs easy to read, if it fails, the build should not be marked as failed, especially since the logs are probably not needed if the rest of the job succeeded.
2017-09-06 16:59:04 +02:00
(cat "$log" | curl --silent -F 'clbin=<-' https://clbin.com) || 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
done
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:
gitlab-ci: build before starting emulator to speed things up The emulator will grab a bunch of RAM, so run assemble before connectedCheck so that the app is mostly built before starting the emulator.
2017-03-17 12:42:59 +01:00
- ./gradlew assembleDebug -PdisablePreDex
gitlab-ci: provide debug info for connected24 failures connected24 tests are frequently failing saying that while an emulator is running, its not compatible. This is bizarre. This just adds debug output to help troubleshoot that.
2017-05-01 11:54:22 +02:00
- android list avd
gitlab-ci: ensure compile platform is installed Avoid broken builds when fdroidclient gets out of sync with ci-images/client. `emulator -no-skin` no longer does anything, but give a warning.
2017-03-17 12:29:45 +01:00
- emulator64-arm -avd fcl-test-$AVD_SDK -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: provide debug info for connected24 failures connected24 tests are frequently failing saying that while an emulator is running, its not compatible. This is bizarre. This just adds debug output to help troubleshoot that.
2017-05-01 11:54:22 +02:00
- adb devices
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:";
gitlab-ci: don't fail build if clbin fails clbin is just for making the logs easy to read, if it fails, the build should not be marked as failed, especially since the logs are probably not needed if the rest of the job succeeded.
2017-09-06 16:59:04 +02:00
(adb -e logcat -d | curl --silent -F 'clbin=<-' https://clbin.com) || true;
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=1;
}
- for log in app/build/reports/*ests/*/*ml
app/build/outputs/*results*/connected/*.xml; do
echo "read $log here:";
gitlab-ci: don't fail build if clbin fails clbin is just for making the logs easy to read, if it fails, the build should not be marked as failed, especially since the logs are probably not needed if the rest of the job succeeded.
2017-09-06 16:59:04 +02:00
(cat "$log" | curl --silent -F 'clbin=<-' https://clbin.com) || true;
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
done
- 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
gitlab-ci: use before and after script for reused chunks It also reduces redundancy by using before_script and after_script blocks.
2016-09-27 16:19:45 +02:00
after_script:
# this file changes every time but should not be cached
- rm -f $GRADLE_USER_HOME/caches/modules-2/modules-2.lock
- rm -fr $GRADLE_USER_HOME/caches/*/plugin-resolution/