-
Task
-
Resolution: Done
-
Major
-
2.15.0.GA
-
None
-
False
-
False
-
Updated the job-config.json file to include these new values for CRW 2.15/2.x:
"NODE_VERSION": {
"2.13": "12.22.3",
"2.14": "12.22.3",
"2.15": "12.22.5",
"2.x": "12.22.5"
},
"YARN_VERSION": {
"2.13": "1.22.5",
"2.14": "1.22.5",
"2.15": "1.22.17",
"2.x": "1.22.17"
}
Yet after running the jenkins node updater in https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/system/job/jenkins-node-setup/30/ to update both the x86_64-rhel8-p1 and x86_64-rhel8-p2 nodes...
16:19:36 [WARNING]: The loop variable 'item' is already in use. You should set the 16:19:36 `loop_var` value in the `loop_control` option for the task to something else to 16:19:36 avoid variable collisions and unexpected behavior. 16:19:36 included: /mnt/hudson_workspace/workspace/system/jenkins-node-setup/ansible-scripts/roles/nodejs/tasks/node.yml for 127.0.0.1 => (item={'key': '2.13', 'value': '12.22.3'}) 16:19:36 included: /mnt/hudson_workspace/workspace/system/jenkins-node-setup/ansible-scripts/roles/nodejs/tasks/node.yml for 127.0.0.1 => (item={'key': '2.14', 'value': '12.22.3'}) 16:19:36 included: /mnt/hudson_workspace/workspace/system/jenkins-node-setup/ansible-scripts/roles/nodejs/tasks/node.yml for 127.0.0.1 => (item={'key': '2.15', 'value': '12.22.5'}) 16:19:36 included: /mnt/hudson_workspace/workspace/system/jenkins-node-setup/ansible-scripts/roles/nodejs/tasks/node.yml for 127.0.0.1 => (item={'key': '2.x', 'value': '12.22.5'})
... I see the crw_env script for 2.15 has not been updated:
$➔ for n in x86_64-rhel8-p1 x86_64-rhel8-p2 x86_64-rhel8-p3; do echo $n; ssh $n "~/crw_env 2.15; yarn --version; node --version"; echo; done x86_64-rhel8-p1 Now using node v12.22.5 (npm v6.14.14) 1.22.5 v12.22.3 x86_64-rhel8-p2 Now using node v12.22.5 (npm v6.14.14) 1.22.5 v12.22.3 x86_64-rhel8-p3 Now using node v12.22.3 (npm v6.14.13) << older version of npm 1.22.5 v12.22.3
- mentioned on
