kamp/fdroidserver
1
0
Fork 0
mirror of https://gitlab.com/fdroid/fdroidserver.git synced 2024-11-09 17:00:12 +01:00
Code Activity
12682f063d
fdroidserver/buildserver/provision-gradle

46 lines
1.3 KiB
Plaintext
Raw Normal View History

buildserver: unpack gradle versions with provisioning shell script This was not using anything special from chef, so do it in a shell script instead. This makes the script easier for the python/shell people, and probably uses less memory, since chef is a memory hog. This might even make the provision go faster since it uploads the whole script as a file to the VM, then runs it there. I think chef sends each command via SSH.
2016-06-15 15:25:57 +02:00
#!/bin/bash
build: improve gradle experience This expands the gradle wrapper shell script used by the buildserver for usage outside the buildserver environment. It also allows downloading whitelisted versions of gradle if they are not yet deployed to the buildserver by simply upsating the copy of fdroidserver (in contrast to having to reprovision the whole buildserver). We first move the buildserver/gradle shell script to the repo root as gradlew-fdroid, as it's an fdroid specific gradle wrapper. We also now sync it inside the build VM before each build. We then add a list of whitelisted gradle distributions taken from the makebuildserver script. The script additionally now reads two env vars which tell it where to expect installed versions of gradle and where it might store downloaded gradle .zip files. Both of those are configurable from config.py. As the first should normally just be a subdir of the second it's not exposed in the example config.py but only used by the buildserver config.py. Default config now uses this internal gradle wrapper but a path to a custom wrapper or specific gradle distribution can still be set from config.py. Closes fdroid/fdroidserver#98 Ref: fdroid/fdroidserver#370
2018-07-08 17:34:17 +02:00
set -ex
buildserver: unpack gradle versions with provisioning shell script This was not using anything special from chef, so do it in a shell script instead. This makes the script easier for the python/shell people, and probably uses less memory, since chef is a memory hog. This might even make the provision go faster since it uploads the whole script as a file to the VM, then runs it there. I think chef sends each command via SSH.
2016-06-15 15:25:57 +02:00
provision-gradle: skip versions older than 2.2.1 These are almost never used now and still can be downloaded on-demand.
2018-11-27 16:29:44 +01:00
# version compare magic
vergte() {
printf '%s\n%s' "$1" "$2" | sort -C -V -r
}
buildserver: unpack gradle versions with provisioning shell script This was not using anything special from chef, so do it in a shell script instead. This makes the script easier for the python/shell people, and probably uses less memory, since chef is a memory hog. This might even make the provision go faster since it uploads the whole script as a file to the VM, then runs it there. I think chef sends each command via SSH.
2016-06-15 15:25:57 +02:00
test -e /opt/gradle/versions || mkdir -p /opt/gradle/versions
cd /opt/gradle/versions
for f in /vagrant/cache/gradle-*.zip; do
ver=`echo $f | sed 's,.*gradle-\([0-9][0-9.]*\).*\.zip,\1,'`
provision-gradle: skip versions older than 2.2.1 These are almost never used now and still can be downloaded on-demand.
2018-11-27 16:29:44 +01:00
# only use versions greater or equal 2.2.1
if vergte $ver 2.2.1 && [ ! -d /opt/gradle/versions/${ver} ]; then
buildserver: unpack gradle versions with provisioning shell script This was not using anything special from chef, so do it in a shell script instead. This makes the script easier for the python/shell people, and probably uses less memory, since chef is a memory hog. This might even make the provision go faster since it uploads the whole script as a file to the VM, then runs it there. I think chef sends each command via SSH.
2016-06-15 15:25:57 +02:00
unzip -qq $f
mv gradle-${ver} /opt/gradle/versions/${ver}
fi
done
chmod -R a+rX /opt/gradle
test -e /opt/gradle/bin || mkdir -p /opt/gradle/bin
build: improve gradle experience This expands the gradle wrapper shell script used by the buildserver for usage outside the buildserver environment. It also allows downloading whitelisted versions of gradle if they are not yet deployed to the buildserver by simply upsating the copy of fdroidserver (in contrast to having to reprovision the whole buildserver). We first move the buildserver/gradle shell script to the repo root as gradlew-fdroid, as it's an fdroid specific gradle wrapper. We also now sync it inside the build VM before each build. We then add a list of whitelisted gradle distributions taken from the makebuildserver script. The script additionally now reads two env vars which tell it where to expect installed versions of gradle and where it might store downloaded gradle .zip files. Both of those are configurable from config.py. As the first should normally just be a subdir of the second it's not exposed in the example config.py but only used by the buildserver config.py. Default config now uses this internal gradle wrapper but a path to a custom wrapper or specific gradle distribution can still be set from config.py. Closes fdroid/fdroidserver#98 Ref: fdroid/fdroidserver#370
2018-07-08 17:34:17 +02:00
ln -fs /home/vagrant/fdroidserver/gradlew-fdroid /opt/gradle/bin/gradle
chown -h vagrant.vagrant /opt/gradle/bin/gradle
chown vagrant.vagrant /opt/gradle/versions
chmod 0755 /opt/gradle/versions
provision-gradle: disable daemon and block HTTP repos closes #624 #712
2020-01-14 23:27:40 +01:00
GRADLE_HOME=/home/vagrant/.gradle
test -d $GRADLE_HOME/ || mkdir $GRADLE_HOME/
cat <<EOF > $GRADLE_HOME/gradle.properties
# builds are not reused, so the daemon is a waste of time
org.gradle.daemon=false
buildserver: use long timeouts for gradle downloads default is 30 seconds, this uses 10 minutes to avoid things like: * What went wrong: A problem occurred configuring root project 'org.fdroid.fdroid'. > Could not resolve all files for configuration ':classpath'. > Could not download auto-value.jar (com.google.auto.value:auto-value:1.5.2) > Could not get resource 'https://repo.maven.apache.org/maven2/com/google/auto/value/auto-value/1.5.2/auto-value-1.5.2.jar'. > Read timed out * https://stackoverflow.com/a/49646993 * https://github.com/gradle/gradle/issues/4629#issuecomment-393182135 * https://github.com/gradle/gradle/pull/3371/files
2020-02-12 13:58:47 +01:00
# set network timeouts to 10 minutes
# https://github.com/gradle/gradle/pull/3371/files
systemProp.http.connectionTimeout=600000
systemProp.http.socketTimeout=600000
systemProp.org.gradle.internal.http.connectionTimeout=600000
systemProp.org.gradle.internal.http.socketTimeout=600000
provision-gradle: disable daemon and block HTTP repos closes #624 #712
2020-01-14 23:27:40 +01:00
EOF
provision-gradle: remove fake proxy configuration The prohibition of HTTP causes connection errors on some builds: IOException: https://dl.google.com/android/repository/addons_list-3.xml java.net.ConnectException: Connection refused (Connection refused) IOException: https://dl.google.com/android/repository/addons_list-2.xml java.net.ConnectException: Connection refused (Connection refused) IOException: https://dl.google.com/android/repository/addons_list-1.xml java.net.ConnectException: Connection refused (Connection refused) Failed to download any source lists! Partly revert a746917022cc7412ac8f922cbab64d1bf6b5f2d5.
2020-03-15 15:34:25 +01:00
provision-gradle: disable daemon and block HTTP repos closes #624 #712
2020-01-14 23:27:40 +01:00
chown -R vagrant.vagrant $GRADLE_HOME/
chmod -R a+rX $GRADLE_HOME/
Copy Permalink