Skip to content

ci: use new arc cluster #47897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 30, 2025
Merged

ci: use new arc cluster #47897

merged 1 commit into from
Jul 30, 2025

Conversation

jkleinsc
Copy link
Member

@jkleinsc jkleinsc commented Jul 28, 2025

Description of Change

This PR moves our GHA runners to a new arc cluster with better capacity.

Checklist

Release Notes

Notes: none

@jkleinsc jkleinsc added target/35-x-y PR should also be added to the "35-x-y" branch. target/36-x-y PR should also be added to the "36-x-y" branch. target/37-x-y PR should also be added to the "37-x-y" branch. target/38-x-y PR should also be added to the "38-x-y" branch. labels Jul 29, 2025
@jkleinsc jkleinsc marked this pull request as ready for review July 29, 2025 21:55
@jkleinsc jkleinsc requested a review from a team as a code owner July 29, 2025 21:55
@jkleinsc jkleinsc changed the title ci: try new arc cluster ci: use new arc cluster Jul 30, 2025
Copy link
Member

@VerteDinde VerteDinde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Comment on lines +39 to +44
echo "const fs = require('fs');" > gettoken.js
echo "const fileContents = fs.readFileSync('sas-token', 'utf8');" >> gettoken.js
echo "const token = JSON.parse(fileContents);" >> gettoken.js
echo "console.log(token[process.argv[2]])" >> gettoken.js
sas_token=$(node ./gettoken.js sasToken)
account_name=$(node ./gettoken.js accountName)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
echo "const fs = require('fs');" > gettoken.js
echo "const fileContents = fs.readFileSync('sas-token', 'utf8');" >> gettoken.js
echo "const token = JSON.parse(fileContents);" >> gettoken.js
echo "console.log(token[process.argv[2]])" >> gettoken.js
sas_token=$(node ./gettoken.js sasToken)
account_name=$(node ./gettoken.js accountName)
sas_token=$(jq -r '.sasToken' sas-token)
account_name=$(jq -r '.accountName' sas-token)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JQ is not available on Windows runners.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can make this a todo along with #47897 (comment)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah for sure, didn't realize jq wasn't in that image, should be easy to install with choco in our scripts

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shell: powershell
if: ${{ inputs.target-platform == 'win' }}
run: |
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -Type DWord
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we take this as a TODO to load this into the windows runner image?

@jkleinsc jkleinsc merged commit 0d0cbaf into main Jul 30, 2025
193 of 199 checks passed
@jkleinsc jkleinsc deleted the test-new-cluster branch July 30, 2025 17:45
@release-clerk
Copy link

release-clerk bot commented Jul 30, 2025

No Release Notes

@trop
Copy link
Contributor

trop bot commented Jul 30, 2025

I have automatically backported this PR to "38-x-y", please check out #47912

@trop
Copy link
Contributor

trop bot commented Jul 30, 2025

I have automatically backported this PR to "35-x-y", please check out #47913

@trop
Copy link
Contributor

trop bot commented Jul 30, 2025

I have automatically backported this PR to "36-x-y", please check out #47914

@trop trop bot added in-flight/35-x-y and removed target/38-x-y PR should also be added to the "38-x-y" branch. labels Jul 30, 2025
@trop
Copy link
Contributor

trop bot commented Jul 30, 2025

I have automatically backported this PR to "37-x-y", please check out #47915

@trop trop bot added in-flight/36-x-y in-flight/37-x-y and removed target/35-x-y PR should also be added to the "35-x-y" branch. target/36-x-y PR should also be added to the "36-x-y" branch. target/37-x-y PR should also be added to the "37-x-y" branch. labels Jul 30, 2025
jkleinsc added a commit that referenced this pull request Jul 30, 2025
@trop trop bot added merged/38-x-y PR was merged to the "38-x-y" branch. merged/37-x-y PR was merged to the "37-x-y" branch. merged/36-x-y PR was merged to the "36-x-y" branch. merged/35-x-y PR was merged to the "35-x-y" branch. and removed in-flight/38-x-y in-flight/37-x-y in-flight/36-x-y in-flight/35-x-y labels Jul 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged/35-x-y PR was merged to the "35-x-y" branch. merged/36-x-y PR was merged to the "36-x-y" branch. merged/37-x-y PR was merged to the "37-x-y" branch. merged/38-x-y PR was merged to the "38-x-y" branch. semver/none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants