Page MenuHomeGitPull.it

Build 1221
PassedPublic

Properties

Drydock: Sign and Publish Builded APK Files

When
Completed at Tue, Apr 28, 12:49 · Built for 13 s
Status
Passed
Description

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:

https://lab.reyboz.it/builds/libre-busto/

1 empty log is hidden Show all logs.

Build Log 6188 (remote - stdout)
25 - 50 - 100 - Unlimited Lines

587724862720 res/yg.9.png (OK)
587824863155 res/yj.xml (OK - compressed)
587924863552 res/yn.png (OK)
588024866036 res/z-.9.png (OK)
588124866300 res/z9.9.png (OK)
588224866760 res/zE.png (OK)
588324867124 res/zG.xml (OK - compressed)
588424867444 res/zR.png (OK)
588524870245 res/zR.xml (OK - compressed)
588624870736 res/zV.9.png (OK)
588724873239 res/zc.xml (OK - compressed)
588824873692 res/ze.png (OK)
588924882047 res/zp.xml (OK - compressed)
589024882306 res/zq.xml (OK - compressed)
589124882616 res/zr.png (OK)
589224885435 res/zs.xml (OK - compressed)
589324885707 res/zu.xml (OK - compressed)
589424886685 res/zv.xml (OK - compressed)
589524887968 resources.arsc (OK)
5896Verification successful
5897[INFO][2026-04-28 10:49:19] APK ALIGNED D232-x86_64-aligned.apk: apksigner... creating D232-x86_64-signed.apk
5898[INFO][2026-04-28 10:49:21] APK ALIGNED SIGNED D232-x86_64-signed.apk: calculating sha256sum...
5899[INFO][2026-04-28 10:49:21] Cleaning old artifacts
5900[INFO][2026-04-28 10:49:21] Done
5901

Drydock: Assemble debug APK using Docker Fabione asd

When
Completed at Tue, Apr 28, 12:49 · Built for 4 m, 15 s
Status
Passed
Description

This step will build an .apk using Gradle using this fantastic Docker image:

https://gitlab.com/fabmazz/android-fdroid-build-container/-/tree/ubuntu

Source code of this build step:

https://gitpull.it/source/libre-busto-ci-cd/browse/master/bin/fdroid-docker-builder.sh

TODO: Use the official image by Fabio Mazza, when the "DESIRED_UID" / "DESIRED_GID" features will be merged.

Build Log 6187 (remote - stderr)
25 - 50 - 100 - Unlimited Lines

1+ docker run -e DESIRED_UID=1004 -e DESIRED_GID=1004 --rm -v /var/drydock/workingcopy-112/repo/libre-busto:/home/vagrant/appbuild:Z fdroid-asder launch_build_local -Dorg.gradle.jvmargs=-Xmx2g --stacktrace assembleGitpull
2Note: Some input files use or override a deprecated API.
3Note: Recompile with -Xlint:deprecation for details.
4/home/vagrant/appbuild/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]
5 <uses-permission android:name="android.permission.ACCESS_MOCK_LOCATION"/>
6 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7
8 Explanation for issues of type "MockLocation":
9 Using a mock location provider (by requiring the permission
10 android.permission.ACCESS_MOCK_LOCATION) should only be done in debug
11 builds (or from tests). In Gradle projects, that means you should only
12 request this permission in a test or debug source set specific manifest
13 file.
14
15 To fix this, create a new manifest file in the debug folder and move the
16 <uses-permission> element there. A typical path to a debug manifest
17 override file in a Gradle project is src/debug/AndroidManifest.xml.
18
191 error
20
21

Build Log 6186 (remote - stdout)
25 - 50 - 100 - Unlimited Lines

144> Task :app:mergeDexGitpull
145> Task :app:processGitpullJavaRes
146> Task :app:compileGitpullArtProfile
147> Task :app:mergeGitpullJavaResource
148> Task :app:lintVitalAnalyzeGitpull
149> Task :app:lintVitalReportGitpull
150
151> Task :app:lintVitalGitpull
152
153> Task :app:packageGitpull
154> Task :app:createGitpullApkListingFileRedirect
155> Task :app:assembleGitpull
156
157[Incubating] Problems report is available at: file:///home/vagrant/appbuild/build/reports/problems/problems-report.html
158
159Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
160
161You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
162
163For 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.
164
165BUILD SUCCESSFUL in 4m 4s
16656 actionable tasks: 56 executed
167==> Build completed
168

Lease BusTO Working Copy

When
Completed at Tue, Apr 28, 12:44 · Built for 2 s
Status
Passed

Abort Older Builds

When
Completed at Tue, Apr 28, 12:44 · Built instantly
Status
Passed