| Passed |
The command is:
/home/phabricator-android-builder/repos/libre-busto-ci-cd/bin/publish-latest-branch-build.sh ${buildable.revision}Source code:
https://gitpull.it/source/libre-busto-ci-cd/browse/master/bin/publish-latest-branch-build.sh
(ex P23)
This step will copy the built .apk to an indexed HTTP directory exposed by Apache, signing them:
| 1 | PHP Fatal error: Uncaught HTTPFutureHTTPResponseStatus: [HTTP/403] |
|---|---|
| 2 | <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
| 3 | <html><head> |
| 4 | <title>403 Forbidden</title> |
| 5 | </head><body> |
| 6 | <h1>Forbidden</h1> |
| 7 | <p>You don't have permission to access this resource.</p> |
| 8 | <hr> |
| 9 | <address>Apache/2.4.59 (Debian) Server at gitpull.it Port 443</address> |
| 10 | </body></html> in /home/www-data/gitpull.it/arcanist/src/future/http/BaseHTTPFuture.php:384 |
| 11 | Stack trace: |
| 12 | #0 /home/www-data/gitpull.it/arcanist/src/future/http/HTTPSFuture.php(552): BaseHTTPFuture->parseRawHTTPResponse('HTTP/1.1 403 Fo...') |
| 13 | #1 /home/www-data/gitpull.it/arcanist/src/future/Future.php(65): HTTPSFuture->isReady() |
| 14 | #2 /home/www-data/gitpull.it/arcanist/src/future/FutureProxy.php(35): Future->updateFuture() |
| 15 | #3 /home/www-data/gitpull.it/arcanist/src/future/Future.php(65): FutureProxy->isReady() |
| 16 | #4 /home/www-data/gitpull.it/arcanist/src/future/FutureIterator.php(224): Future->updateFuture() |
| 17 | #5 /home/www-data/gitpull.it/arcanist/src/future/FutureIterator.php(190): FutureIterator->next() |
| 18 | #6 [inter in /home/www-data/gitpull.it/arcanist/src/future/http/BaseHTTPFuture.php on line 384 |
| 19 |
| 6087 | |
|---|---|
| 6088 | APK for **arm64\-v8a**: |
| 6089 | [Download D209\-arm64\-v8a\-signed\.apk](https://lab.reyboz.it/builds/libre-busto/D209-arm64-v8a-signed.apk) |
| 6090 | APK sha256: `52d2ab00cb38e7ec581e53fc9c8050851c9c14921782e8a295c28247cb8af4da` |
| 6091 | |
| 6092 | APK for **armeabi\-v7a**: |
| 6093 | [Download D209\-armeabi\-v7a\-signed\.apk](https://lab.reyboz.it/builds/libre-busto/D209-armeabi-v7a-signed.apk) |
| 6094 | APK sha256: `35d6c81ae0643d4f9a7c319d92290991107ae8ac84d9930f82f12e10ba7d10c4` |
| 6095 | |
| 6096 | APK for **universal**: |
| 6097 | [Download D209\-universal\-signed\.apk](https://lab.reyboz.it/builds/libre-busto/D209-universal-signed.apk) |
| 6098 | APK sha256: `691adee820e352bea86e5df01f4adf54ec238f1595755a5585a51d40bcd6f01c` |
| 6099 | |
| 6100 | APK for **x86**: |
| 6101 | [Download D209\-x86\-signed\.apk](https://lab.reyboz.it/builds/libre-busto/D209-x86-signed.apk) |
| 6102 | APK sha256: `fcfe6d89232823a9721b57da8ba9f5284722f513fbb721d2ad6963e2dca77d30` |
| 6103 | |
| 6104 | APK for **x86\_64**: |
| 6105 | [Download D209\-x86\_64\-signed\.apk](https://lab.reyboz.it/builds/libre-busto/D209-x86_64-signed.apk) |
| 6106 | APK sha256: `2d6613078b373cdc9eee2df3687d2929c48fd907cc018a6335537ca0177efde1` |
| 6107 | |
| 6108 | Adding bipbop Comment to D209 |
| 6109 | [INFO][2025-11-20 12:20:57] Cleaning old artifacts |
| 6110 | [INFO][2025-11-20 12:20:57] Done |
| 6111 |
| Passed |
This step will build an .apk using Gradle.
sudo apt install openjdk-11-jre-headless
Then aliased this gradle:
https://gitlab.com/fdroid/fdroidserver/-/blob/master/gradlew-fdroid
| 1 | Note: Some input files use or override a deprecated API. |
|---|---|
| 2 | Note: Recompile with -Xlint:deprecation for details. |
| 3 | /var/drydock/workingcopy-79/repo/libre-busto/app/src/gitpull/AndroidManifest.xml:4: Error: Mock locations should only be requested in a test or debug-specific manifest file (typically src/debug/AndroidManifest.xml) [MockLocation] |
| 4 | <uses-permission android:name="android.permission.ACCESS_MOCK_LOCATION"/> |
| 5 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 6 | |
| 7 | Explanation for issues of type "MockLocation": |
| 8 | Using a mock location provider (by requiring the permission |
| 9 | android.permission.ACCESS_MOCK_LOCATION) should only be done in debug |
| 10 | builds (or from tests). In Gradle projects, that means you should only |
| 11 | request this permission in a test or debug source set specific manifest |
| 12 | file. |
| 13 | |
| 14 | To fix this, create a new manifest file in the debug folder and move the |
| 15 | <uses-permission> element there. A typical path to a debug manifest |
| 16 | override file in a Gradle project is src/debug/AndroidManifest.xml. |
| 17 | |
| 18 | 1 error |
| 19 | |
| 20 |
| 96 | > Task :app:generateGitpullLintVitalReportModel |
|---|---|
| 97 | > Task :app:processGitpullJavaRes |
| 98 | > Task :app:mergeGitpullJavaResource |
| 99 | > Task :app:mergeDexGitpull |
| 100 | > Task :app:compileGitpullArtProfile |
| 101 | > Task :app:lintVitalAnalyzeGitpull |
| 102 | > Task :app:lintVitalReportGitpull |
| 103 | |
| 104 | > Task :app:lintVitalGitpull |
| 105 | |
| 106 | > Task :app:packageGitpull |
| 107 | > Task :app:createGitpullApkListingFileRedirect |
| 108 | > Task :app:assembleGitpull |
| 109 | |
| 110 | [Incubating] Problems report is available at: file:///var/drydock/workingcopy-79/repo/libre-busto/build/reports/problems/problems-report.html |
| 111 | |
| 112 | Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. |
| 113 | |
| 114 | You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. |
| 115 | |
| 116 | For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. |
| 117 | |
| 118 | BUILD SUCCESSFUL in 1m 1s |
| 119 | 54 actionable tasks: 53 executed, 1 up-to-date |
| 120 |
| Passed |
Clean Gradle directory to avoid nasty errors like:
| 1 | Found 8.13 via distributionUrl |
|---|---|
| 2 | Running /home/phabricator-android-builder/versions/8.13/bin/gradle clean |
| 3 | > Task :app:clean |
| 4 | |
| 5 | [Incubating] Problems report is available at: file:///var/drydock/workingcopy-79/repo/libre-busto/build/reports/problems/problems-report.html |
| 6 | |
| 7 | Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. |
| 8 | |
| 9 | You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. |
| 10 | |
| 11 | For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. |
| 12 | |
| 13 | BUILD SUCCESSFUL in 3s |
| 14 | 1 actionable task: 1 executed |
| 15 |
| Passed |
| Passed |