-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Correct ARMv8 to aarch64 in Jenkins #1837
Comments
Clearing assignment as I don't have access to the machines to restart the Jenkins agent |
I'm tempted to switch them all over to |
Yeah, that seems fair - should I rename the issue ? Should ARMv7 remain ARMv7? (I noticed that the job just refers to it as |
@sxa I'm happy to pick this up, as it's blocking me on #1716 , but presumably I'm going to need access to all of the (The following is a list of machines that I don't have access to. I do have it for the rest of the ARMv8 nodes in the inventory)
|
@Willsparker Any update on this? |
Still waiting on @sxa so I can get access to the above nodes |
Quick update on this - the Linaro machines are not currently in production, the scaleway ones are going to get decomissioned (and are armv7 not armv8), the packet aarch64 ones listed above are also to be decomissioned soon. We'll need to consider what to do with the macos ones ... |
Still considering keeping armv8 since aarch64 will become ambiguous across armv8, armv8.2 (Required by Dragonwell) and the upcoming armv9 |
After some discussions with someone at ARM I've come to the conclusion that standardising on |
The new ones added in #2478 #3586 have all been added as
We should bump up the priority of this for usability/simplicity reasons - adding to Q4 plan. |
Found as a part of #1716 (comment)
As suggested by @sxa (#1806 (review)), we should change the Jenkins name of the following machines, so they match the inventory.yml, i.e. remove the
l
fromarmv(7|8)l
:Should just be a case of changing their names, and restarting the Jenkins agent.
The text was updated successfully, but these errors were encountered: