Error was:
Some problems were found with the configuration of task ':koverMergedHtmlReport' (type 'KoverHtmlTask').
- Gradle detected a problem with the following location: '/home/runner/work/element-x-android/element-x-android/features/analytics/api/build/tmp/kotlin-classes/release'.
Reason: Task ':koverMergedHtmlReport' uses this output of task ':features:analytics:api:compileReleaseKotlin' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:
1. Declare task ':features:analytics:api:compileReleaseKotlin' as an input of ':koverMergedHtmlReport'.
2. Declare an explicit dependency on ':features:analytics:api:compileReleaseKotlin' from ':koverMergedHtmlReport' using Task#dependsOn.
3. Declare an explicit dependency on ':features:analytics:api:compileReleaseKotlin' from ':koverMergedHtmlReport' using Task#mustRunAfter.
...
Update the label/description - labels are compulsory and end up in the issue body
Split out signoff from tasklist - that way signoffs do not count towards the total tasks in the issue
I created 2 additional test users to use them as MXID we lookup during room creation.
I.e. we will not login as those users, it's just 2 known MXIDs that we know exist so we can look them up.
- https://github.com/vector-im/element-x-android/issues/409
If the gradle build fails for some reason, the script should
bail out instead of carrying on and pushing a commit that
deletes all the screenshots[1]!
`set -e` simply makes the script return the appropriate
exit code immediately if any of the subcommands fails.
[1] e.g.
a58834240e
Maplibre uses semver, so pre-releases look like `1.2.3-something`,
but renovate defaults to a looser version matching when using
maven (to allow for weird things like 1.2.3-android being stable).
Uses https://github.com/nschloe/action-cached-lfs-checkout where we're using git-lfs.
This is a wrapper around `actions/checkout@v3` which uses `actions/cache@v3` to cache the files on LFS to avoid downloading them every time and spare LFS bandwidth.
Move the dependency check job from the quality workflow that
runs on every PR to the nightly reports workflow. This sometimes
flakes as it does a _lot_ of HTTP requests. It's less intrusive
if that happens outside of the PR workflow.
Also change the nightly job that runs tests to use LFS, so it
actually has access to screenshots :)
The sonar task is still broken, but it seems like an upstream bug:
https://community.sonarsource.com/t/sonar-plugin-4-1-0-3113-4-2-0-3129-errors/91568
* Update the Rust SDK to v0.1.7.
* Try to have the same setup for the build apk job and maestro.
* Add option to run maestro manually.
* Update to v0.1.9 (0.1.7 and 0.1.8 were broken in x86_64).
* Update AGP to 8.0.0.
* Set JAVA_HOME to JDK17
* Update lint version.
* Use right JDK for dependency analysis, replace deprecated env var.
* Upgrade to Gradle 8.1.
* Remove `@Supress(DSL_SCOPE_VIOLATION)` as it's no longer needed.
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Benoit Marty