com.zell mbc.medilog/lastbuild 5318

From F-Droid
Revision as of 18:58, 23 October 2020 by Robot (Talk | contribs) (Build log)

Jump to: navigation, search

Installed Android Tools

Build Log

' failed on server for com.zell_mbc.medilog:'


== Installed Android Tools ==

2020-10-23 18:57:35,203 INFO: Creating log directory
2020-10-23 18:57:35,203 INFO: Creating temporary directory
2020-10-23 18:57:35,204 INFO: Creating output directory
2020-10-23 18:57:40,440 INFO: Using git version 2.11.0
2020-10-23 18:57:40,440 INFO: Building version (5318) of com.zell_mbc.medilog
2020-10-23 18:57:46,190 INFO: Getting source for revision v1.9.0.2
2020-10-23 18:57:51,156 INFO: Creating file at build/com.zell_mbc.medilog/
2020-10-23 18:57:51,157 INFO: Updating file at build/com.zell_mbc.medilog/app/
2020-10-23 18:57:51,164 INFO: Cleaned build.gradle of keysigning configs at build/com.zell_mbc.medilog/app/build.gradle
2020-10-23 18:57:51,176 INFO: Cleaning Gradle project...
2020-10-23 18:58:05,692 ERROR: Could not build app com.zell_mbc.medilog: Error cleaning com.zell_mbc.medilog:
==== detail begin ====
Found 6.4.1 via distributionUrl
Running /opt/gradle/versions/6.4.1/bin/gradle clean

Welcome to Gradle 6.4.1!

Here are the highlights of this release:
 - Support for building, testing and running Java Modules
 - Precompiled script plugins for Groovy DSL
 - Single dependency lock file per project

For more details see

To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon:
Daemon will be stopped at the end of the build stopping after processing

FAILURE: Build failed with an exception.

* Where:
Build file '/home/vagrant/build/com.zell_mbc.medilog/app/build.gradle' line: 1

* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin [id '']
   > Minimum supported Gradle version is 6.5. Current version is 6.4.1. If using the gradle wrapper, try editing the distributionUrl in /home/vagrant/build/com.zell_mbc.medilog/gradle/wrapper/ to

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at

==== detail end ====