-
-
Notifications
You must be signed in to change notification settings - Fork 170
ansible: test-joyent-smartos*-x64-[34] #2014
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
Conversation
|
@mhdawson @rvagg This is related to #2005 (comment) I'd like to link this to some issue that describes why we are doing this but haven't found one. |
mhdawson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Looking into this. |
|
|
@nodejs/platform-smartos I'll bang away at above, but would appreciate any advice from people who have used SmartOS for more than 5 minutes (which is me). |
|
This gets further: |
|
Turns out ccache can only be compiled as C99, and that its configure system is not compatible with solaris' |
|
Next error:
|
|
I think the conditionals were malformed, not sure how that snuck in, see 7f99d3f |
|
With that last change, jenkins/worker/create runs to completetion. |
|
Rebased onto master after #2010 landed. |
|
I cloned the existing -2 nodes into the new -3/-4 nodes, updated the secrets, re-ansibled, now they need firewall rules setup by @mhdawson (or someone else in @nodejs/build-infra ). |
|
Firewall rules setup |
|
I made the configure changes conditional on the OS, but will wait to confirm they work until the test job is quiet before re-ansibling them: https://ci.nodejs.org/job/node-test-commit-smartos |
|
Again, this is the hard way of doing it, I'm not objecting, just pointing it out. If you add additional machines then you have to make new entries here, secrets, ci firewall and jenkins UI. Then you'll have to do the inverse of all 4 of those things when you remove the old machines. If you just replace old machines you just have to update the ip address here and in ci firewall. You get to reuse secrets and the Jenkins entry. If you're worried about downtime because there's multiple people and potentially multiple days, these are just test machines so you could disable the entire test-node-commit-smartos and they'll be mostly unused. Edit: Michael mentions some of the reasoning here: #2003 (comment), I'm not trying to get in the way here, just pointing out how I do it to minimise effort and duplication. Take it as you will. Thanks for taking on this work. |
|
I don't have strong feelings, and the extra work is already done. As a note - the amount of time spent on copying machine defs was a 10th of the time spent getting ansilble to run without errors. I removed the silencing of deprecation warnings, since some people find them useful. |
|
|
||
| - name: "ccache : prepare for compilation - smartos" | ||
| when: os|startswith("smartos") | ||
| shell: bash ./configure CPPFLAGS=-std=c99 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I remember this but may have resorted to an older version of ccache to get around it. Good change, thanks for figuring it out!
|
builds green on the new smartos hosts: |
No description provided.