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

107 lines
3.5 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: push nightly builds to fdroid repo on gitlab If a repo is set with the gitlab-ci Secret Variable DEBUG_KEYSTORE and there is a repo named the same as this repo with -nightly appended, then this will automatically generate an fdroid repo of each build produced by gitlab-ci runs on the master branch. closes fdroidserver#256
2017-10-11 23:48:12 +02:00
stages:
- test
- deploy
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`
gitlab-ci: convert connected10 job to connected14 #1379
2018-04-19 12:28:50 +02:00
- echo y | $ANDROID_HOME/tools/bin/sdkmanager "platforms;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
gitlab-ci: replace clbin uploads with GitLab CI Artifacts This gathers all files that are not tracked by git into a named ZIP file, which is available for 1 week to download from the Pipelines page for the fork that ran the build.
2018-01-12 13:50:28 +01:00
.test-template: &test-template
artifacts:
name: "${CI_PROJECT_PATH}_${CI_JOB_STAGE}_${CI_COMMIT_REF_NAME}_${CI_COMMIT_SHA}"
paths:
- logcat.txt
- app/build/reports
- app/build/outputs/*ml
- app/build/outputs/apk
expire_in: 1 week
when: on_failure
after_script:
- echo "Download debug artifacts from https://gitlab.com/${CI_PROJECT_PATH}/-/jobs"
gitlab-ci: order "tests" job so most important are run first This means that we can decide whether to ignore the style tests if the rest of the more meaningful tests pass.
2018-02-05 17:05:35 +01:00
# Run the most important first. Then we can decide whether to ignore
# the style tests if the rest of the more meaningful tests pass.
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:
gitlab-ci: push nightly builds to fdroid repo on gitlab If a repo is set with the gitlab-ci Secret Variable DEBUG_KEYSTORE and there is a repo named the same as this repo with -nightly appended, then this will automatically generate an fdroid repo of each build produced by gitlab-ci runs on the master branch. closes fdroidserver#256
2017-10-11 23:48:12 +02:00
stage: test
gitlab-ci: replace clbin uploads with GitLab CI Artifacts This gathers all files that are not tracked by git into a named ZIP file, which is available for 1 week to download from the Pipelines page for the fork that ran the build.
2018-01-12 13:50:28 +01:00
<<: *test-template
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
auto-disable preDexLibraries on CI systems preDexing helps repeat builds run faster, but slows down builds that do not have any caching. CI builds start from scratch each time. Turns out that GitLab CI, Travis CI, Circle CI, and probably many others all define the "CI" environment variable, so its easy to detect when running in a CI environment. This makes things a lot cleaner. * https://docs.gitlab.com/ce/ci/variables/README.html * https://docs.travis-ci.com/user/environment-variables/ * https://circleci.com/docs/2.0/env-vars/ * https://github.com/codepath/android_guides/wiki/Setting-up-Travis-CI * https://stackoverflow.com/questions/23137764/building-a-debug-apk
2017-10-25 22:15:40 +02:00
- ./gradlew assemble
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
gitlab-ci: order "tests" job so most important are run first This means that we can decide whether to ignore the style tests if the rest of the more meaningful tests pass.
2018-02-05 17:05:35 +01:00
- ./gradlew test
auto-disable preDexLibraries on CI systems preDexing helps repeat builds run faster, but slows down builds that do not have any caching. CI builds start from scratch each time. Turns out that GitLab CI, Travis CI, Circle CI, and probably many others all define the "CI" environment variable, so its easy to detect when running in a CI environment. This makes things a lot cleaner. * https://docs.gitlab.com/ce/ci/variables/README.html * https://docs.travis-ci.com/user/environment-variables/ * https://circleci.com/docs/2.0/env-vars/ * https://github.com/codepath/android_guides/wiki/Setting-up-Travis-CI * https://stackoverflow.com/questions/23137764/building-a-debug-apk
2017-10-25 22:15:40 +02:00
- ./gradlew lint
gitlab-ci: order "tests" job so most important are run first This means that we can decide whether to ignore the style tests if the rest of the more meaningful tests pass.
2018-02-05 17:05:35 +01:00
- ./gradlew pmd || export EXITVALUE=1
- ./gradlew checkstyle || export EXITVALUE=1
- ./tools/check-format-strings.py
- ./tools/remove-unused-and-blank-translations.py
- echo "These are unused or blank translations that should be removed:"
- git --no-pager diff --ignore-all-space --name-only --exit-code || export EXITVALUE=1
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
move errorprone config to its own gitlab CI job
2018-02-13 20:19:45 +01:00
errorprone:
stage: test
script:
- cat config/errorprone.gradle >> app/build.gradle
- ./gradlew assembleDebug
allow_failure: true
gitlab-ci: convert connected10 job to connected14 #1379
2018-04-19 12:28:50 +02:00
connected14:
gitlab-ci: push nightly builds to fdroid repo on gitlab If a repo is set with the gitlab-ci Secret Variable DEBUG_KEYSTORE and there is a repo named the same as this repo with -nightly appended, then this will automatically generate an fdroid repo of each build produced by gitlab-ci runs on the master branch. closes fdroidserver#256
2017-10-11 23:48:12 +02:00
stage: test
gitlab-ci: replace clbin uploads with GitLab CI Artifacts This gathers all files that are not tracked by git into a named ZIP file, which is available for 1 week to download from the Pipelines page for the fork that ran the build.
2018-01-12 13:50:28 +01:00
<<: *test-template
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
variables:
gitlab-ci: convert connected10 job to connected14 #1379
2018-04-19 12:28:50 +02:00
AVD_SDK: "14"
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
script:
auto-disable preDexLibraries on CI systems preDexing helps repeat builds run faster, but slows down builds that do not have any caching. CI builds start from scratch each time. Turns out that GitLab CI, Travis CI, Circle CI, and probably many others all define the "CI" environment variable, so its easy to detect when running in a CI environment. This makes things a lot cleaner. * https://docs.gitlab.com/ce/ci/variables/README.html * https://docs.travis-ci.com/user/environment-variables/ * https://circleci.com/docs/2.0/env-vars/ * https://github.com/codepath/android_guides/wiki/Setting-up-Travis-CI * https://stackoverflow.com/questions/23137764/building-a-debug-apk
2017-10-25 22:15:40 +02:00
- ./gradlew assembleDebug
gitlab-ci: convert connected10 job to connected14 #1379
2018-04-19 12:28:50 +02:00
- echo y | $ANDROID_HOME/tools/bin/sdkmanager "platforms;android-$AVD_SDK"
- echo y | $ANDROID_HOME/tools/bin/sdkmanager "system-images;android-${AVD_SDK};default;armeabi-v7a"
- echo no | android --verbose create avd --name fcl-test-$AVD_SDK --target android-$AVD_SDK
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 &
gitlab-ci: replace clbin uploads with GitLab CI Artifacts This gathers all files that are not tracked by git into a named ZIP file, which is available for 1 week to download from the Pipelines page for the fork that ran the build.
2018-01-12 13:50:28 +01:00
- ./gradlew connectedCheck || adb -e logcat -d '*:E' > logcat.txt
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:
gitlab-ci: push nightly builds to fdroid repo on gitlab If a repo is set with the gitlab-ci Secret Variable DEBUG_KEYSTORE and there is a repo named the same as this repo with -nightly appended, then this will automatically generate an fdroid repo of each build produced by gitlab-ci runs on the master branch. closes fdroidserver#256
2017-10-11 23:48:12 +02:00
stage: test
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"
gitlab-ci: replace clbin uploads with GitLab CI Artifacts This gathers all files that are not tracked by git into a named ZIP file, which is available for 1 week to download from the Pipelines page for the fork that ran the build.
2018-01-12 13:50:28 +01:00
<<: *test-template
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:
auto-disable preDexLibraries on CI systems preDexing helps repeat builds run faster, but slows down builds that do not have any caching. CI builds start from scratch each time. Turns out that GitLab CI, Travis CI, Circle CI, and probably many others all define the "CI" environment variable, so its easy to detect when running in a CI environment. This makes things a lot cleaner. * https://docs.gitlab.com/ce/ci/variables/README.html * https://docs.travis-ci.com/user/environment-variables/ * https://circleci.com/docs/2.0/env-vars/ * https://github.com/codepath/android_guides/wiki/Setting-up-Travis-CI * https://stackoverflow.com/questions/23137764/building-a-debug-apk
2017-10-25 22:15:40 +02:00
- ./gradlew assembleDebug
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: replace clbin uploads with GitLab CI Artifacts This gathers all files that are not tracked by git into a named ZIP file, which is available for 1 week to download from the Pipelines page for the fork that ran the build.
2018-01-12 13:50:28 +01:00
- ./gradlew connectedCheck || adb -e logcat -d '*:E' > logcat.txt
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: push nightly builds to fdroid repo on gitlab If a repo is set with the gitlab-ci Secret Variable DEBUG_KEYSTORE and there is a repo named the same as this repo with -nightly appended, then this will automatically generate an fdroid repo of each build produced by gitlab-ci runs on the master branch. closes fdroidserver#256
2017-10-11 23:48:12 +02:00
deploy_nightly:
stage: deploy
only:
- master
script:
gitlab-ci: set nightly build app name to "F-Nightly"
2017-12-06 16:29:51 +01:00
- sed -i
's,<string name="app_name">.*</string>,<string name="app_name">F-Nightly</string>,'
app/src/main/res/values*/strings.xml
# add this nightly repo as a enabled repo
gitlab-ci: add nightly repo to deploy builds as default enabled
2017-12-02 22:50:28 +01:00
- sed -i -e '/<\/string-array>/d' -e '/<\/resources>/d' app/src/main/res/values/default_repos.xml
- echo "<item>${CI_PROJECT_PATH}-nightly</item>" >> app/src/main/res/values/default_repos.xml
- echo "<item>${CI_PROJECT_URL}-nightly/raw/master/fdroid/repo</item>" >> app/src/main/res/values/default_repos.xml
- cat config/nightly-repo/repo.xml >> app/src/main/res/values/default_repos.xml
gitlab-ci: set nightly build app name to "F-Nightly"
2017-12-06 16:29:51 +01:00
# build the APKs!
gitlab-ci: nightly builds using `fdroid nightly`
2018-01-04 23:00:55 +01:00
- ./gradlew assembleDebug
- fdroid nightly -v
gitlab-ci: push nightly builds to fdroid repo on gitlab If a repo is set with the gitlab-ci Secret Variable DEBUG_KEYSTORE and there is a repo named the same as this repo with -nightly appended, then this will automatically generate an fdroid repo of each build produced by gitlab-ci runs on the master branch. closes fdroidserver#256
2017-10-11 23:48:12 +02: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/