Closed smlambert closed 1 week ago
Noting that, at present, the new TRSS machine is not connected to jenkins. If you need me to assist with that let me know (I only realised that today as I disconnected the old one which isn't there any more after seeing errors in the jenkins system log)
Run locally and see that sometimes npm run docker-down
doesn't always shut everything down. Think it may be good to update the package.json file L9 to:
"docker-down": "docker compose down --remove-orphans",
Run locally and see that sometimes
npm run docker-down
doesn't always shut everything down.
Yeah I've noted that in the message you get when you log into the Adoptium TRSS. I've definitely had to issue manual docker stop
operations before.
I have updated the package.json file in https://github.com/adoptium/aqa-test-tools/pull/868, so now orphans will get cleaned up, so will not expect future issues with things hanging open after docker-down. That sync script has been run manually on the machine. Once trss.adoptium.net is added to Jenkins, I will update the sync job in Jenkins to run weekly.
From the work that took place under https://github.com/adoptium/aqa-test-tools/issues/404 and the shift to running TRSS & its components inside of containers, we need to update the TRSS synch script / job.
The script is here and the ci.adoptium.net job is here.
We can update the script to stop docker, run the git pull / update and then start docker again (see instructions here).