-
Notifications
You must be signed in to change notification settings - Fork 166
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
jenkins: openssl1.1.0 not supported on node.js 12+ #1711
Conversation
nodedjs/master advertises its version as v12.0.0-pre, so I hope this will apply to it. |
made a test job to test this: BTW: we might want to add a test with a shared 1.1.1 |
P.S. meanwhile for testing you can trigger the job and un-checking the incompatible configuration. |
Sorry, I really don't know enough about jenkins to know how to test this. I did https://ci.nodejs.org/job/node-test-commit-linux-containered/11123/ from #1711 (comment), unchecking some things that shouldn't be run, but I'm not at all sure what that tested. Should that have used the groovy changes in this file? What am I looking for? What do I do next to get this landed, or confirm that it does whats intended? |
I'd like another @nodejs/build review.
This run https://ci.nodejs.org/job/temp2-node-test-commit-linux-containered/4/console seems to verify it excludes as expected:
|
Testing https://ci.nodejs.org/job/temp2-node-test-commit-linux-containered/5/console with
|
I don't have perms to make an openssl-1.1.1 containerd build. It looks like the conditional step for I can't really tell from https://ci.nodejs.org/computer/test-softlayer-ubuntu1604_sharedlibs_container-x64-5/ what the container is. If can get ssh access to test-softlayer-ubuntu1604_docker-x64-1 I could poke around, and try to see where openssl1.1.0 is (a docker container, somewhere on the fs, not sure). I suspect an openssl 1.1.1 Does anyone in @nodejs/build want to take a shot at configuring this? If not, I'll ask for access. I'll need a bit of guidance, I've never done any jenkins configuration before. /cc @mhdawson @miladfarca |
I think openssl-1.1.1 is already in the container, based on
I'm not in @nodejs/build, but wouldn't mind volunteering to configure this if you'd prefer someone with more experience editing Jenkins job configuration. I don't have access to this particular job, but do already have access to the CitGM, node-stresss and node-report jobs. |
If no new Containers are needed. I'll give this a go. |
Ahh, again it seems like @rvagg already set everything up 🙇 . Just needed to flip a switch. BTW, it's set up to run for node >= 9 (linked with shared 1.1.1) it that correct? |
Yay! Thanks for the help @refack @rvagg and @richardlau Until nodejs/node#26270 lands, the 1.1.1 containerd test should only run for node |
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
https://ci.nodejs.org/job/node-test-commit-linux-containered/11164/
https://ci.nodejs.org/job/node-test-commit-linux-containered/11165/
|
https://ci.nodejs.org/job/node-test-commit-linux-containered/11164/nodes=ubuntu1604_sharedlibs_openssl111_x64/testReport/junit/(root)/test/parallel_test_bootstrap_modules/ 💢 |
I don't think those test failures are related to the changes here: nodejs/node#26520 |
Ok, so we're back in business https://ci.nodejs.org/job/node-test-commit-linux-containered/jobConfigHistory/showDiffFiles?timestamp1=2019-02-28_17-50-31×tamp2=2019-03-08_10-30-49 |
Thanks @refack |
See: nodejs/node#26209 (comment)