You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had modified the test jenkins cloud settings so that it could only provision 3 of the 4 vm's for each architecture in order to ensure that release always had capacity to provision a new instance. In doing so, jenkins stranded an instance, so even though the test jenkins was only aware of 3 instances, orka had 4 provisioned, thus there was no capacity for release.
I remedied this yesterday, and all the builds have caught back up.
Jenkins was still having counting issues with how many nodes it thought it had vs how many it actually was allowed to manage, as such, the test instance had all of the x86 resources when the release was happening.
Can we coordinate when the release does go out so that Im aware/available? I'm not seeing these github pings in a timely fashion, and I would like to be on hand to ensure it goes smoothly.
Given that #4053 has been resolved, and that we've got the priorities settled between the testing and release infra (we have room for 4 VM's per architecture, and test will only ever create 3, so there is always at least 1 vm dedicated to releases per architecture), I believe this can be closed now.
Activity
richardlau commentedon Feb 3, 2025
CC @ryanaslett
FYI This would block the (delayed from last week) Node.js 20.18.3 proposal (cc @marco-ippolito ).
ryanaslett commentedon Feb 5, 2025
I had modified the test jenkins cloud settings so that it could only provision 3 of the 4 vm's for each architecture in order to ensure that release always had capacity to provision a new instance. In doing so, jenkins stranded an instance, so even though the test jenkins was only aware of 3 instances, orka had 4 provisioned, thus there was no capacity for release.
I remedied this yesterday, and all the builds have caught back up.
marco-ippolito commentedon Feb 5, 2025
Thanks!
marco-ippolito commentedon Feb 6, 2025
We still having some issues https://ci-release.nodejs.org/job/iojs+release/10793/ on for the job
osx13-x64-release-tar.This job is blocking the release CI
ryanaslett commentedon Feb 7, 2025
Jenkins was still having counting issues with how many nodes it thought it had vs how many it actually was allowed to manage, as such, the test instance had all of the x86 resources when the release was happening.
Can we coordinate when the release does go out so that Im aware/available? I'm not seeing these github pings in a timely fashion, and I would like to be on hand to ensure it goes smoothly.
marco-ippolito commentedon Feb 7, 2025
I'd reschedule the v20.x release for monday
aduh95 commentedon Feb 10, 2025
v20.18.3 release went smoothly today. I'll try to release v22.14.0 tomorrow, hoping for the best
ryanaslett commentedon Apr 2, 2025
Given that #4053 has been resolved, and that we've got the priorities settled between the testing and release infra (we have room for 4 VM's per architecture, and test will only ever create 3, so there is always at least 1 vm dedicated to releases per architecture), I believe this can be closed now.