Steps to add a new infocenter (help.eclipse.org)

1. Add the latest p2_repo_dir to the Choice Parameter in simrel.create_and_publish_infocenter_pipeline in the Jenkinsfile! (TODO: Automate!)
   • Dir can be found here: https://download.eclipse.org/releases/ <release> (e.g. releases/2022-03/202203161000)
2. Run simrel.create_and_publish_infocenter_pipeline to package a new infocenter
   • Set the release_name parameter (e.g. 2022-03)
   • Make sure that use_latest_platform is enabled (unless you know exactly what you are doing)
   • Select latest p2_repo_dir
   • Wait for the build to finish
   • Set build description, e.g. “2022-03 with 4.23 platform“
3. Deploy infocenter on cluster (EF internal)
   • If you haven’t already, checkout the help.eclipse.org repo locally
     git clone https://github.com/eclipse-simrel/help.eclipse.org
   • Pull the latest changes: git pull
   • Make sure you are connected to the cluster (so you can deploy stuff from the command line)
   • Create infocenter YAML:
     k8s/createInfoCenter_yaml.sh <release_name> <sha256>
     • <release_name> e.g. 2022-03
     • <sha256> (without the sha256: prefix) (copy from the last lines in the simrel.publish_infocenter_pipeline console log)
   • Deploy infocenter:
     k8s/deployInfoCenter.sh <release_name>
     • <release_name> e.g. 2022-03
   • Check that the new infocenter pod is running on the cluster: oc get pods -n infocenter
4. Shutdown oldest infocenter on the cluster and remove the folder in the repo (EF internal)
   

   k8s/removeInfoCenter.sh <release_name>

5. Commit the changes in /org.eclipse.simrel.tools/infoCenter/k8s:
   • New directory for the latest release (e.g. 2022-03)
   • Remove oldest directory
6. Adapt nginx configuration in puppet (EF internal)
   
   • Commit the change and wait for nginx to reload (=> manually reload nginx for now!)
7. Check that https://help.eclipse.org/2022-03 works as expected after the deployment
   This might require something like:
   wget -O - --tries=1 --header='X-Cache-Bypass: true' https://help.eclipse.org/2022-03
8. Update https://help.eclipse.org/latest to point to the latest info center (EF internal)
   • Update k8s/route_latest.yml
   • Deploy the route with oc apply -f route_latest.yml
   • Check that https://help.eclipse.org/latest shows the latest version
     This might require something like:
     wget -O - --tries=1 --header='X-Cache-Bypass: true' http://help.eclipse.org/latest
9. Add new (and remove oldest) info center in the shell script in simrel.check_infocenter

Update former latest infocenter top banner to state “Past release”

1. Run simrel.create_and_publish_infocenter_pipeline
   • Set the release_name parameter (e.g. 2021-12)
   • Choose correct p2_repo_dir
   • Select the “past_release” checkbox !!
   • Wait for the build to finish
   • Fix build description, e.g. “2021-06 with 4.21 platform (past release)“
2. Get new sha265 from the console log and change it in the deployment YAML file e.g. /help.eclipse.org/charts/infocenter/values-2023-12.yaml
3. Deploy infocenter to cluster (EF internal)
   • Re-deploy with: helm upgrade 2023-12 charts/infocenter -f charts/infocenter/values-2023-12.yaml --namespace infocenter
4. Double-check that banner is now updated (might required X-Cache-Bypass wget call)
5. Commit and push /help.eclipse.org/charts/infocenter/values-2023-12.yaml