doc: change references of ci.adoptopenjdk.net to ci.adoptium.net (#2942)

.github/ISSUE_TEMPLATE/testcasefail.md

@@ -11,7 +11,7 @@ To make it easy for the infrastructure team to repeat and diagnose, please
 answer the following questions:
 
 - test suite/name (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET)?
-- a link into recent `Test_` job on https://ci.adoptopenjdk.net which showed the failure
+- a link into recent `Test_` job on https://ci.adoptium.net which showed the failure
 - **Hyperlink** to re-run in Grinder: 
 - Is there an existing issue elsewhere covering this?
 - Which machine(s) does it work on?

.github/PULL_REQUEST_TEMPLATE.md

@@ -9,6 +9,6 @@ the requirements below.
 - [ ] commit message has one of the [standard prefixes](https://github.com/adoptium/infrastructure/blob/master/CONTRIBUTING.md#commit-messages)
 - [ ] [faq.md](https://github.com/adoptium/infrastructure/blob/master/FAQ.md) updated if appropriate
 - [ ] other documentation is changed or added (if applicable)
-- [ ] playbook changes run through [VPC](https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/) or [QPC](https://ci.adoptopenjdk.net/view/Tooling/job/QEMUPlaybookCheck/) (if you have access)
+- [ ] playbook changes run through [VPC](https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/) or [QPC](https://ci.adoptium.net/view/Tooling/job/QEMUPlaybookCheck/) (if you have access)
 - [ ] VPC/QPC not applicable for this PR
 - [ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

.github/workflows/build_vagrant.yml

@@ -30,7 +30,7 @@ jobs:
           echo "Box Exists - Do Nothing"
         else
           echo "No Box - Download From Jenkins And Import"
-          wget https://ci.adoptopenjdk.net/userContent/vagrant/Solaris10.box.gz
+          wget https://ci.adoptium.net/userContent/vagrant/Solaris10.box.gz
           CKSUM=`shasum -a 256 ./Solaris10.box.gz|cut -d" " -f1`
           if [ "$CKSUM" = "0879215f4bf03f5e125addb139d0b5a49a4f8a258297b765cf1f22a8a7ee3309" ]
           then

CONTRIBUTING.md

@@ -118,18 +118,18 @@ is not getting enough attention, let one the team know via the
 
 To test changes made to our ansible playbooks, we have the following test jobs which you can use to validate your pull request:
 
-[VagrantPlaybookCheck](https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/)
+[VagrantPlaybookCheck](https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/)
    - Tests changes made to the Unix or Windows playbook.
    - Suitable to test changes made which concern the x86_64 tasks of the ansible playbooks
    - Requires authorised access to kick off (ping a member of the [infrastructure](https://github.com/adoptium/infrastructure#infrastructure-core) team if necessary)
 
-[QemuPlaybookCheck](https://ci.adoptopenjdk.net/view/Tooling/job/QEMUPlaybookCheck/)
+[QemuPlaybookCheck](https://ci.adoptium.net/view/Tooling/job/QEMUPlaybookCheck/)
    - Tests changes made to the Unix playbook
    - Suitable to test changes made which concern non x86_64 tasks of the ansible playbooks, such as s390x, arm32, aarch64, riscv and ppc64le
    - Requires authorised access to kick off (ping a member of the [infrastructure](https://github.com/adoptium/infrastructure#infrastructure-core) team if necessary)
 
 `QEMU-playbook-check` pull request Label
-   - Similar to [QemuPlaybookCheck](https://ci.adoptopenjdk.net/view/Tooling/job/QEMUPlaybookCheck/), but runs as a github workflow
+   - Similar to [QemuPlaybookCheck](https://ci.adoptium.net/view/Tooling/job/QEMUPlaybookCheck/), but runs as a github workflow
    - Does not require authorised access to kick off, just add the `QEMU-playbook-check` label to your pull request
    - See https://github.com/adoptium/infrastructure/blob/master/.github/workflows/build_qemu.yml for supported platforms
 

FAQ.md

@@ -81,9 +81,9 @@ have at the moment:
 
 | Dockerfile | Image | Platforms  | Where is this built? | In use?
 |---|---|---|---|---|
-| [Centos7](./ansible/docker/Dockerfile.CentOS7) | [`adoptopenjdk/centos7_build_image`](https://hub.docker.com/r/adoptopenjdk/centos7_build_image) | linux on amd64, arm64, ppc64le | [Jenkins](https://ci.adoptopenjdk.net/job/centos7_docker_image_updater/) | Yes
+| [Centos7](./ansible/docker/Dockerfile.CentOS7) | [`adoptopenjdk/centos7_build_image`](https://hub.docker.com/r/adoptopenjdk/centos7_build_image) | linux on amd64, arm64, ppc64le | [Jenkins](https://ci.adoptium.net/job/centos7_docker_image_updater/) | Yes
 | [Centos6](./ansible/docker/Dockerfile.CentOS6) | [`adoptopenjdk/centos6_build_image`](https://hub.docker.com/r/adoptopenjdk/centos6_build_image)| linux/amd64 | [GH Actions](.github/workflows/build.yml) | Yes
-| [Alpine3](./ansible/docker/Dockerfile.Alpine3) | [`adoptopenjdk/alpine3_build_image`](https://hub.docker.com/r/adoptopenjdk/alpine3_build_image) | linux/x64 & linux/arm64 | [Jenkins](https://ci.adoptopenjdk.net/job/centos7_docker_image_updater/) | Yes
+| [Alpine3](./ansible/docker/Dockerfile.Alpine3) | [`adoptopenjdk/alpine3_build_image`](https://hub.docker.com/r/adoptopenjdk/alpine3_build_image) | linux/x64 & linux/arm64 | [Jenkins](https://ci.adoptium.net/job/centos7_docker_image_updater/) | Yes
 
 When a change lands into master, the relevant dockerfiles are built using
 the appropriate CI system listed in the table above by configuring them with
@@ -214,7 +214,7 @@ should have an underscore `_` prepended to it.
 
 If you are making a change which might have a negative effect on the
 playbooks on other platforms, be sure to run it through the
-[VagrantPlaybookCheck](https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/)
+[VagrantPlaybookCheck](https://ci.adoptium.net/job/VagrantPlaybookCheck/)
 job first. This job takes a branch from a fork of the
 `adoptium/infrastructure` repository as a parameter and runs the playbooks
 against a variety of Operating Systems using Vagrant and the scripts in
@@ -223,7 +223,7 @@ to validate them.
 
 ## Jenkins access
 
-The AdoptOpenJDK Jenkins server at [https://ci.adoptopenjdk.net](https://ci.adoptopenjdk.net) is used for all the
+The Adoptium Jenkins server at [https://ci.adoptium.net](https://ci.adoptium.net) is used for all the
 builds and testing automation. Since we're as open as possible, general read
 access is enabled. For others, access is controlled via github teams (via
 the Jenkins `Github Authentication Plugin` as follows. (Links here won't work for
@@ -236,8 +236,8 @@ most people as the teams are restricted access)
 - [jenkins-admins](https://github.com/orgs/AdoptOpenJDK/teams/jenkins-admins/members) as you might expect has access to Administer anything
 
 Some jobs within jenkins, such as the
-[build signing job](https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/sign_build)
-and [Release tool job](https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/refactor_openjdk_release_tool)
+[build signing job](https://ci.adoptium.net/job/build-scripts/job/release/job/sign_build)
+and [Release tool job](https://ci.adoptium.net/job/build-scripts/job/release/job/refactor_openjdk_release_tool)
 are restricted further via the `Enable project-based security` section of
 the job definition. In the case of those two in particular it's `jenkins-admins` and
 `release` teams only who have access to them respectively.
@@ -251,7 +251,7 @@ To add a new system:
 3. Add it to bastillion (requires extra privileges) so that all of the appropriate admin keys are deployed to the system (Can be delayed for expediency by putting AWX key into `~root/.ssh/authorized_keys`)
 4. Create a PR to add the machine to [inventory.yml](https://github.com/adoptium/infrastructure/blob/master/ansible/inventory.yml) (See NOTE at end of the list)
 5. Once merged, run the ansible scripts on it - ideally via AWX (Ensure the project and inventory sources are refreshed, then run the appropriate `Deploy **** playbook` template with a `LIMIT` of the new machine name)
-6. Add it to Jenkins and verify a typical job runs on it if you can and add the appropriate tags.  When adding systems for use by test pipelines, verify all of the different types of tests can successfully run on that system by launching an [AQA_Test_Pipeline](https://ci.adoptopenjdk.net/job/AQA_Test_Pipeline/) job and setting LABEL parameter to the hostname of the machine.  Once you verify that the AQA_Test_Pipeline runs cleanly, you can add the appropriate test labels (as per LABELs defined in the aqa-tests [PLATFORM_MAP](https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/openjdk_tests#L3)).
+6. Add it to Jenkins and verify a typical job runs on it if you can and add the appropriate tags.  When adding systems for use by test pipelines, verify all of the different types of tests can successfully run on that system by launching an [AQA_Test_Pipeline](https://ci.adoptium.net/job/AQA_Test_Pipeline/) job and setting LABEL parameter to the hostname of the machine.  Once you verify that the AQA_Test_Pipeline runs cleanly, you can add the appropriate test labels (as per LABELs defined in the aqa-tests [PLATFORM_MAP](https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/openjdk_tests#L3)).
 
 NOTE ref inventory: If you are adding a new type of machine (`build`, `perf` etc.) you should also add it to
    [adoptopenjdk_yaml.py](https://github.com/adoptium/infrastructure/blob/master/ansible/plugins/inventory/adoptopenjdk_yaml.py#L45)

ONBOARDING.md

@@ -28,7 +28,7 @@ For [@admin_infrastructure](https://github.com/orgs/AdoptOpenJDK/teams/admin_inf
 
 ## External Services
 
-### [ci.adoptopenjdk.net](https://ci.adoptopenjdk.net)
+### [ci.adoptium.net](https://ci.adoptium.net)
 
 All infrastructure members have full admin access to the jenkins follower section allowing them to create, delete and update followers.
 

ansible/README.md

@@ -182,7 +182,7 @@ We have some automation for running under Vagrant which we use to validate
 playbook changes before they are merged. See the
 [pbTestScripts](pbTestScripts/) folder for more info. The scripts from there
 are run on jenkins in the
-[VagrantPlaybookCheck](https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/) job
+[VagrantPlaybookCheck](https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/) job
 
 Any additional help in setting up Vagrant with Virtualbox can be found [here](https://www.vagrantup.com/intro/getting-started/index.html)
 

ansible/inventory.yml

@@ -25,7 +25,7 @@ hosts:
 
       - hetzner:
           ubuntu1604-x64-1: {ip: 78.47.239.96, description: nagios.adoptopenjdk.net}
-          ubuntu2004-x64-1: {ip: 78.47.239.97, description: ci.adoptopenjdk.net}
+          ubuntu2004-x64-1: {ip: 78.47.239.97, description: ci.adoptium.net}
 
       - ibmcloud:
           vagrant-x64-1: {ip: 150.239.60.120, description: Bare metal machine to run vagrantPlaybookCheck and qemuPlaybookCheck}

ansible/pbTestScripts/README.md

@@ -3,7 +3,7 @@
 Most people will not need to run this directly, but if you can it will
 reduce the likelihood of breaking things when you adjust the playbooks.
 These scripts can be invoked via the
-[VagrantPlaybookCheck](https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/)
+[VagrantPlaybookCheck](https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/)
 job if you have access to our jenkins, and they take 60-90 minutes to run
 on the UNIX/Linux-based platforms, but closer to three hours for Windows.
 

ansible/pbTestScripts/vagrantPlaybookCheck.sh

@@ -236,7 +236,7 @@ startVMPlaybook()
 	[ ! -r $HOME/.ssh/known_hosts ] && touch $HOME/.ssh/known_hosts && chmod 644 $HOME/.ssh/known_hosts
 	ssh-keygen -R $(cat playbooks/AdoptOpenJDK_Unix_Playbook/hosts.unx)
 
-	sed -i -e "s/.*hosts:.*/- hosts: all/g" playbooks/AdoptOpenJDK_Unix_Playbook/main.yml
+	sed -i -e "s/.*hosts:.*/  hosts: all/g" playbooks/AdoptOpenJDK_Unix_Playbook/main.yml
 	awk '{print}/^\[defaults\]$/{print "private_key_file = id_rsa"; print "remote_tmp = $HOME/.ansible/tmp"; print "timeout = 60"}' < ansible.cfg > ansible.cfg.tmp && mv ansible.cfg.tmp ansible.cfg
 
 	ansible-playbook $verbosity -i playbooks/AdoptOpenJDK_Unix_Playbook/hosts.unx -u vagrant -b --skip-tags adoptopenjdk,jenkins${skipFullSetup} playbooks/AdoptOpenJDK_Unix_Playbook/main.yml 2>&1 | tee $WORKSPACE/adoptopenjdkPBTests/logFiles/$gitFork.$newGitBranch.$OS.log
@@ -319,7 +319,7 @@ startVMPlaybookWin()
 	echo "This is the content of hosts.win : " && cat playbooks/AdoptOpenJDK_Windows_Playbook/hosts.win
 
 	# Changes the value of "hosts" in main.yml
-	sed -i'' -e "s/.*hosts:.*/- hosts: all/g" playbooks/AdoptOpenJDK_Windows_Playbook/main.yml
+	sed -i'' -e "s/.*hosts:.*/  hosts: all/g" playbooks/AdoptOpenJDK_Windows_Playbook/main.yml
 	# Uncomments and sets the ansible_password to 'vagrant', in adoptopenjdk_variables.yml
 	sed -i'' -e "s/.*ansible_password.*/ansible_password: vagrant/g" playbooks/AdoptOpenJDK_Windows_Playbook/group_vars/all/adoptopenjdk_variables.yml
 	# If "credssp" isn't found in adoptopenjdk_variables.yml

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/DockerStatic/README.md

@@ -6,10 +6,10 @@ A verbose description of our static docker container system can be found in the
 The DockerStatic ansible role provides allows us to automate the setup of our dockerhost machines using the [dockerhost.yml](https://github.com/adoptium/infrastructure/blob/master/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/dockerhost.yml) playbook.
 
 ## Our current Dockerhost machines
-* [docker-packet-ubuntu2004-amd-1](https://ci.adoptopenjdk.net/computer/docker-packet-ubuntu2004-amd-1/)
-* [docker-packet-ubuntu2004-intel-1](https://ci.adoptopenjdk.net/computer/docker-packet-ubuntu2004-intel-1/)
-* [docker-packet-ubuntu2004-armv8-1](https://ci.adoptopenjdk.net/computer/docker-packet-ubuntu2004-armv8-1/)
-* [dockerhost-equinix-ubuntu2004-armv8-1](https://ci.adoptopenjdk.net/computer/dockerhost-equinix-ubuntu2004-armv8-1/)
+* [docker-packet-ubuntu2004-amd-1](https://ci.adoptium.net/computer/docker-packet-ubuntu2004-amd-1/)
+* [docker-packet-ubuntu2004-intel-1](https://ci.adoptium.net/computer/docker-packet-ubuntu2004-intel-1/)
+* [docker-packet-ubuntu2004-armv8-1](https://ci.adoptium.net/computer/docker-packet-ubuntu2004-armv8-1/)
+* [dockerhost-equinix-ubuntu2004-armv8-1](https://ci.adoptium.net/computer/dockerhost-equinix-ubuntu2004-armv8-1/)
 
 
 ## Setting up a new DockerStatic container
@@ -30,7 +30,7 @@ If you would like to setup an individual container on one of these machines, fol
 
 `docker run --restart unless-stopped -p {{ PORT }}:22 --cpus=2.0 --memory=6G --detach --name {{ name }} {{ tag }}`
 
-* Finally, go to https://ci.adoptopenjdk.net/computer/new and create a new jenkins node for this container.
+* Finally, go to https://ci.adoptium.net/computer/new and create a new jenkins node for this container.
 
 **NOTE**
 If you are creating a new container with the intention of replacing a container with an older OS, follow the above steps to create the new container. Then:

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Nagios_Plugins/tasks/additional_plugins/check_label

@@ -14,7 +14,7 @@
 
 #!/usr/bin/env bash
 
-# Nagios Plugin to check the percentage of machines online for a given label on ci.adoptopenjdk.net
+# Nagios Plugin to check the percentage of machines online for a given label on ci.adoptium.net
 
 if [ -z $1 ] || [ -z $2 ] || [ -z $3 ]; then
   echo "UNKNOWN - Invalid arguments"
@@ -28,13 +28,13 @@ if ! command -v jq &> /dev/null; then
 fi
 
 # Get list of machines in label
-mapfile -t machine_array < <(curl -s https://ci.adoptopenjdk.net/label/$1/api/json | jq -r '.nodes[] | .nodeName')
+mapfile -t machine_array < <(curl -s https://ci.adoptium.net/label/$1/api/json | jq -r '.nodes[] | .nodeName')
 
 # For each machine, query if they're connected
 response_array=()
 for node in ${machine_array[@]}
 do
-  response_array+=($(curl -s "https://ci.adoptopenjdk.net/computer/${node}/api/json" | jq .offline)) 
+  response_array+=($(curl -s "https://ci.adoptium.net/computer/${node}/api/json" | jq .offline)) 
 done
 
 online=0

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Nagios_Plugins/tasks/additional_plugins/nagios_server_plugins/check_agent

@@ -14,7 +14,7 @@
 
 #!/usr/bin/env bash
 
-# Nagios plugin to check if a given agent is connected to ci.adoptopenjdk.net
+# Nagios plugin to check if a given agent is connected to ci.adoptium.net
 
 if [ -z $1 ]; then
   echo "UNKNOWN - Invalid arguments"
@@ -27,7 +27,7 @@ if ! command -v jq &> /dev/null; then
   exit 3
 fi
 
-CURL_RESPONSE=$(curl -s https://ci.adoptopenjdk.net/computer/$1/api/json?pretty=true)
+CURL_RESPONSE=$(curl -s https://ci.adoptium.net/computer/$1/api/json?pretty=true)
 if [[ $? != 0 ]]; then
   echo "UNKNOWN- Failed to get agent information"
   exit 3

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Nagios_Plugins/tasks/additional_plugins/nagios_server_plugins/check_inventory

@@ -69,7 +69,7 @@ mkdir -p $HOME/check_inventory_logs
 logPath="$HOME/check_inventory_logs/check_inventory_`date +%H%M_%d%m%Y`"
 
 nagiosList=$(ls -la /usr/local/nagios/etc/servers/ | awk '/.cfg/ { print $9 }' | cut -d. -f1)
-jenkinsList=$(curl -s https://ci.adoptopenjdk.net/computer/api/json | jq -r '.computer[] | .displayName')
+jenkinsList=$(curl -s https://ci.adoptium.net/computer/api/json | jq -r '.computer[] | .displayName')
 [[ $? != 0 ]] && echo "UNKNOWN- Curl failed" && exit 3
 
 # ran on the Nagios User, so put it somewhere we know it has write access to

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Nagios_Plugins/tasks/additional_plugins/nagios_server_plugins/check_nagios_sync

@@ -69,7 +69,7 @@ logPath="$HOME/check_inventory_logs/check_nagios_sync_`date +%H%M_%d%m%Y`"
 rm -rf "$HOME/check_inventory_logs/check_nagios_sync_*"
 
 nagiosList=$(ls -la /usr/local/nagios/etc/servers/ | awk '/.cfg/ { print $9 }' | cut -d. -f1)
-jenkinsList=$(curl -s https://ci.adoptopenjdk.net/computer/api/json | jq -r '.computer[] | .displayName')
+jenkinsList=$(curl -s https://ci.adoptium.net/computer/api/json | jq -r '.computer[] | .displayName')
 [[ $? != 0 ]] && echo "UNKNOWN- Curl failed" && exit 3
 
 echo "

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Python2.7/tasks/main.yml

@@ -18,7 +18,7 @@
 
 - name: Install Python2.7 to /usr/local/python2
   unarchive:
-    src: https://ci.adoptopenjdk.net/userContent/usrlocalPython27.tar.xz
+    src: https://ci.adoptium.net/userContent/usrlocalPython27.tar.xz
     dest: /usr/local/
     remote_src: yes
     mode: 0755

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/freemarker/tasks/main.yml

@@ -17,7 +17,7 @@
 # https://sourceforge.net/projects/freemarker/files/freemarker/2.3.8/freemarker-2.3.8.tar.gz
 - name: Download and extract freemarker.jar
   unarchive:
-    src: https://ci.adoptopenjdk.net/userContent/freemarker-{{ freemarkerVersion }}.tar.gz
+    src: https://ci.adoptium.net/userContent/freemarker-{{ freemarkerVersion }}.tar.gz
     dest: /tmp/
     remote_src: yes
     mode: 0755
@@ -26,7 +26,7 @@
 
 - name: Download and extract freemarker.jar (Solaris)
   unarchive:
-    src: https://ci.adoptopenjdk.net/userContent/freemarker-{{ freemarkerVersion }}.tar.gz
+    src: https://ci.adoptium.net/userContent/freemarker-{{ freemarkerVersion }}.tar.gz
     dest: /tmp/
     remote_src: yes
     mode: 0755

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/gcc_10/tasks/main.yml

@@ -13,7 +13,7 @@
 
 - name: Download AdoptOpenJDK gcc-10.3 binary
   get_url:
-    url: https://ci.adoptopenjdk.net/userContent/gcc/gcc103.{{ ansible_architecture }}.tar.xz
+    url: https://ci.adoptium.net/userContent/gcc/gcc103.{{ ansible_architecture }}.tar.xz
     dest: '/tmp/ansible-adoptopenjdk-gcc-10.tar.xz'
     force: no
     mode: 0644

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/gcc_11/tasks/main.yml

@@ -13,7 +13,7 @@
 
 - name: Download Adoptium gcc-11.2 binary
   get_url:
-    url: https://ci.adoptopenjdk.net/userContent/gcc/gcc112.{{ ansible_architecture }}.tar.xz
+    url: https://ci.adoptium.net/userContent/gcc/gcc112.{{ ansible_architecture }}.tar.xz
     dest: '/tmp/ansible-adoptopenjdk-gcc-11.tar.xz'
     force: no
     mode: 0644

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/gcc_7/tasks/main.yml

@@ -23,7 +23,7 @@
 
 - name: Download AdoptOpenJDK gcc-7.5.0 binary
   get_url:
-    url: https://ci.adoptopenjdk.net/userContent/gcc/gcc750+ccache.{{ ansible_architecture }}.tar.{{ gccsuffix }}
+    url: https://ci.adoptium.net/userContent/gcc/gcc750+ccache.{{ ansible_architecture }}.tar.{{ gccsuffix }}
     dest: '/tmp/ansible-adoptopenjdk-gcc-7.tar.{{ gccsuffix }}'
     force: no
     mode: 0644

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/gcc_9/tasks/main.yml

@@ -15,7 +15,7 @@
 
 - name: Download AdoptOpenJDK gcc-9.3.0 binary
   get_url:
-    url: https://ci.adoptopenjdk.net/userContent/gcc/gcc930.{{ ansible_architecture }}.tar.xz
+    url: https://ci.adoptium.net/userContent/gcc/gcc930.{{ ansible_architecture }}.tar.xz
     dest: '/tmp/ansible-adoptopenjdk-gcc-9.tar.xz'
     force: no
     mode: 0644

ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/riscv_cross_compiler/tasks/main.yml

@@ -40,7 +40,7 @@
 
 - name: Retrieve and unpack the riscv toolchain
   unarchive:
-    src: https://ci.adoptopenjdk.net/userContent/riscv/riscv_toolchain_linux64.tar.xz
+    src: https://ci.adoptium.net/userContent/riscv/riscv_toolchain_linux64.tar.xz
     dest: /opt/
     remote_src: yes
   when:
@@ -53,7 +53,7 @@
 
 - name: Retrieve and Unpack the fedora sysroot folder
   unarchive:
-    src: https://ci.adoptopenjdk.net/userContent/riscv/fedora28_riscv_smlroot_ssl110gdev.tar.xz
+    src: https://ci.adoptium.net/userContent/riscv/fedora28_riscv_smlroot_ssl110gdev.tar.xz
     dest: /opt/
     remote_src: yes
   when: