tchekai704
/
src-spring-framework
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Spring Framework
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
25366 Commits
19 Branches
274 Tags
318 MiB
Tree: 61cc7c0a93
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '61cc7c0a93'
${ noResults }
src-spring-framework/ci/images/setup.sh

41 lines
1.2 KiB
Raw Normal View History Unescape

Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
#!/bin/bash
set -ex
###########################################################
# UTILS
###########################################################
Upgrade CI container images to Ubuntu Focal
4 years ago
export DEBIAN_FRONTEND=noninteractive
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
apt-get update
Upgrade CI container images to Ubuntu Focal
4 years ago
apt-get install --no-install-recommends -y tzdata ca-certificates net-tools libxml2-utils git curl libudev1 libxml2-utils iptables iproute2 jq fontconfig
ln -fs /usr/share/zoneinfo/UTC /etc/localtime
dpkg-reconfigure --frontend noninteractive tzdata
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
rm -rf /var/lib/apt/lists/*
Publish directly to Maven Central This commit skips the Bintray-related tasks in our CI pipeline and instead relies on Maven Central for publishing Spring Framework artifacts. This commit also updates the CI pipeline to sign the artifacts directly with the `artifactory-resource`. Closes gh-26654
4 years ago
curl https://raw.githubusercontent.com/spring-io/concourse-java-scripts/v0.0.4/concourse-java.sh > /opt/concourse-java.sh
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
###########################################################
# JAVA
###########################################################
mkdir -p /opt/openjdk
Introduce Gradle Toolchain support in build Prior to this commit, the Spring Framework build would rely on setting a custom Java HOME for building all sources and tests with that JDK. This approach is not flexible enough, since we would be testing the source compatibility against a recent JDK, but not a common case experienced by the community: compiling and running application code with a recent JDK and the official, JDK8-based Framework artifacts. This method is also limiting our choice of JDKs to the ones currently supported by Gradle itself. This commit introduces the support of Gradle JVM Toolchains in the Spring Framework build. We can now select a specific JDK for compiling the main SourceSets (Java, Groovy and Kotlin) and another one for compiling and running the test SourceSets: `./gradlew check -PmainToolChain=8 -PtestToolchain=15` Gradle will automatically find the JDKs present on the host or download one automcatically. You can find out about the ones installed on your host using: `./gradlew -q javaToolchains` Finally, this commit also refactors the CI infrastructure to: * only have a single CI image (with all the supported JDKs) * use this new feature to compile with JDK8 but test it against JDK11 and JDK15. Closes gh-25787
4 years ago
pushd /opt/openjdk > /dev/null
Add Java 19 to CI image
2 years ago
for jdk in java17 java18 java19
Introduce Gradle Toolchain support in build Prior to this commit, the Spring Framework build would rely on setting a custom Java HOME for building all sources and tests with that JDK. This approach is not flexible enough, since we would be testing the source compatibility against a recent JDK, but not a common case experienced by the community: compiling and running application code with a recent JDK and the official, JDK8-based Framework artifacts. This method is also limiting our choice of JDKs to the ones currently supported by Gradle itself. This commit introduces the support of Gradle JVM Toolchains in the Spring Framework build. We can now select a specific JDK for compiling the main SourceSets (Java, Groovy and Kotlin) and another one for compiling and running the test SourceSets: `./gradlew check -PmainToolChain=8 -PtestToolchain=15` Gradle will automatically find the JDKs present on the host or download one automcatically. You can find out about the ones installed on your host using: `./gradlew -q javaToolchains` Finally, this commit also refactors the CI infrastructure to: * only have a single CI image (with all the supported JDKs) * use this new feature to compile with JDK8 but test it against JDK11 and JDK15. Closes gh-25787
4 years ago
do
JDK_URL=$( /get-jdk-url.sh $jdk )
mkdir $jdk
pushd $jdk > /dev/null
curl -L ${JDK_URL} | tar zx --strip-components=1
test -f bin/java
test -f bin/javac
popd > /dev/null
done
popd
Add Concourse Build pipeline This commit adds the Concourse build infrastructure under the "ci/" folder. It contains: * "images/", the definitions of container images used in the pipeline * "pipeline.yml" the build pipeline definition * "parameters.yml" the parameters for the pipeline definition * "tasks/" the tasks used by the build pipeline * "scripts/" scripts used by pipeline tasks This first iteration of the Concourse pipeline builds CI container images for JDK8, JDK11, JDK14 and JDK15. These images are used for building and publishing the master branch of Spring Framework using JDK8. Other JDK variants are sanity checks and don't actually publish the produced artifacts. See gh-22490
5 years ago
###########################################################
# GRADLE ENTERPRISE
###########################################################
cd /
mkdir ~/.gradle
Upgrade to Concourse Java Script v0.0.3 This new release has been updated with the version scheme changes.
5 years ago
echo 'systemProp.user.name=concourse' > ~/.gradle/gradle.properties