support Java 17 runtime

[kwonglau]

could we add support for Java 17 runtime

[DaanVleugels]

Is there some way to use corretto 17 while waiting for this version to be supported?

[joschi]

@DaanVleugels You could install Corretto 17 and activate it in your buildspec.yml similar to how it's done for Corretto 8 and 11.

Example:

aws-codebuild-docker-images/ubuntu/standard/5.0/Dockerfile

Lines 344 to 353 in 9282872

	RUN set -ex \
	# Install Corretto 11
	# Note: We will use update-alternatives to make sure JDK11 has higher priority for all the tools
	&& apt-get install -y java-11-amazon-corretto-jdk \
	&& for tool_path in $JAVA_HOME/bin/*; do \
	tool=`basename $tool_path`; \
	update-alternatives --install /usr/bin/$tool $tool $tool_path 10000; \
	update-alternatives --set $tool $tool_path; \
	done \
	&& rm $JAVA_HOME/lib/security/cacerts && ln -s /etc/ssl/certs/java/cacerts $JAVA_HOME/lib/security/cacerts \

aws-codebuild-docker-images/ubuntu/standard/5.0/runtimes.yml

Lines 25 to 43 in 9282872

	corretto11:
	commands:
	- echo "Installing Java version 11 ..."
	- export JAVA_HOME="$JAVA_11_HOME"
	- export JRE_HOME="$JRE_11_HOME"
	- export JDK_HOME="$JDK_11_HOME"
	- |-
	for tool_path in "$JAVA_HOME"/bin/*;
	do tool=`basename "$tool_path"`;
	if [ $tool != 'java-rmi.cgi' ];
	then
	update-alternatives --list "$tool" | grep -q "$tool_path" \
	&& update-alternatives --set "$tool" "$tool_path";
	fi;
	done

[MattFellows]

Just FYI - because I followed this advice - doing so seems to break docker in docker capability, or, more specifically, using any non-managed image seems to prevent using docker in docker currently...

[joschi]

@MattFellows How exactly did you build your custom image? I built one based on ubuntu/standard:5.0 some time ago and I don't remember it breaking DinD.

[DaanVleugels]

@joschi, do you still have your version? I have been trying a little, but bumped against upgrading the Gradle version without breaking the old versions’ builds.

[kevintweber]

There is a PR for this request: #495

[rnferreira]

Any update about this?

[rasensio]

Looks like is stuck. So, for now, installing manually

[joschi]

@rasensio Depending on your build process, looking into Maven Toolchains (see also Introduction to Maven Toolchains) or Gradle Toolchains might be preferable since they also work on local developer machines and that way you don't need to manage JDKs on AWS CodeBuild differently.

[rasensio]

Thanks @joschi . I fixed it just with this in the buildspec.yml

pre_build:
commands:
- echo Nothing to do in the pre_build phase...
- yum install java-17-amazon-corretto-devel -y
- alternatives --set java /usr/lib/jvm/java-17-amazon-corretto.aarch64/bin/java

[braek]

@rasensio Which environment are you using in AWS to make this work?

[rasensio]

@rasensio Which environment are you using in AWS to make this work?

latest amazon linux

[braek]

@rasensio Which environment are you using in AWS to make this work?

latest amazon linux

Thanks for the tip! Managed to get my pipeline completely running now for a project using Java 17.

I still hope Amazon will add a managed image for Java 17 in the near future though.

[AdamBien]

Corretto 17 on AWS CodeBuild and maven are working, but have to be setup manually: https://adambien.blog/roller/abien/entry/installing_java_17_amazon_corretto

However: Corretto 17 installation slows down the build pipeline and is a waste of resources.

Please support Corretto 17 in e.g. aws/codebuild/standard:6.0 to avoid the "Undifferentiated Heavy Lifting" :-)