Skip to content
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

Add Node.js 12 to CIs #4072

Merged
merged 2 commits into from May 31, 2019
Merged

Add Node.js 12 to CIs #4072

merged 2 commits into from May 31, 2019

Conversation

ybiquitous
Copy link
Member

Node.js 12 was released on 2019-04-23, which is the Current Release version.
See https://github.com/nodejs/Release#release-schedule.

image

Which issue, if any, is this issue related to?

Related to #3299.

Is there anything in the PR that needs further explanation?

See Node.js 12 changelog.

@ybiquitous
Copy link
Member Author

The AppVeyor build was failed because of appveyor/ci#2921.

@ybiquitous ybiquitous added the pr: blocked is blocked by another issue or pr label May 6, 2019
@alexander-akait
Copy link
Member

/cc @stylelint/core what do you think about migrate on azure pipelines, i can take care about this

@ntwb
Copy link
Member

ntwb commented May 7, 2019

/cc @stylelint/core what do you think about migrate on azure pipelines, i can take care about this

I'd rather we switched our Windows build to Travis CI per #3716 when we can

@ntwb
Copy link
Member

ntwb commented May 7, 2019

An aside, I've not time to look into this right now, but over in stylelint-config-wordpress I'm getting failed Jest snapshots for Node.js 12, I've restarted the tests numerous times but they continue to fail on v12 but pass on v10 and v8 /shrug

https://travis-ci.org/WordPress-Coding-Standards/stylelint-config-wordpress/builds/529146586

@ntwb
Copy link
Member

ntwb commented May 7, 2019

Actually, Jest has an issue with the weak dependancy on Node.js 12 and it cannot install weak on Node.js 12, thus current Jest is not 100% compatible with v12

See jestjs/jest#8397

@ybiquitous
Copy link
Member Author

ybiquitous commented May 7, 2019

Actually, I also have failed tests on Node 12. I don't know the reason yet... 🤔

Node 12 (failed):
https://travis-ci.com/ybiquitous/stylelint-config-ybiquitous/jobs/197948034

Node 10 (passed):
https://travis-ci.com/ybiquitous/stylelint-config-ybiquitous/jobs/197948035

In my case, tape is used, not Jest.

@alexander-akait
Copy link
Member

/cc @ntwb Travis has poor support lately, and their CI is not very fast, unlike azure pipelines. I migrate on azure pipelines in many OSS projects and commercial and it is awesome

@ybiquitous
Copy link
Member Author

please see also nodejs/node#25060

@alexander-akait
Copy link
Member

Guys let's migrate on azure pipelines, it is really faster and stable

@hudochenkov
Copy link
Member

Let's remove appveyor file from this PR and merge it.

Guys let's migrate on azure pipelines, it is really faster and stable

@evilebottnawi are there articles comparing Azure Pipelines and Travis?

If it's faster I think it's easier to have one CI instead of two. Would you like to create PR so we can see how fast and good it is?

@hudochenkov hudochenkov added PR: needs revision and removed pr: blocked is blocked by another issue or pr labels May 30, 2019
@alexander-akait
Copy link
Member

@hudochenkov no articles, just my experience in webpack and webpack ecosystem

Would you like to create PR so we can see how fast and good it is?

Yes, in my todo (do it tomorrow)

@ybiquitous
Copy link
Member Author

Hi, I try the workaround anyway. 💪
platform is x86 only: because our current builds uses x86 only.

appveyor/ci#2921 (comment)

@ybiquitous
Copy link
Member Author

The workaround works well! 😄

See the build log:
https://ci.appveyor.com/project/stylelint/stylelint/builds/24938272/job/n85a6u2v0wkgwy8s

@alexander-akait
Copy link
Member

WIP on azure pipelines

@hudochenkov
Copy link
Member

We should merge this PR any way to be able to compare time with all Node.js versions.

@alexander-akait
Copy link
Member

Feel free to merge

@hudochenkov hudochenkov merged commit 331edb1 into master May 31, 2019
@hudochenkov hudochenkov deleted the ci-node-12 branch May 31, 2019 14:07
install:
- ps: Install-Product node $env:nodejs_version
# Workaround from https://github.com/appveyor/ci/issues/2921#issuecomment-486727727
# https://www.appveyor.com/docs/lang/nodejs-iojs/#installing-any-version-of-nodejs-or-iojs
Copy link
Member

Choose a reason for hiding this comment

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

One thing this shows is how out of date the AppVeyor dos are :(

They continue to reference Node.js v5.x and iojs 🤦🏼‍♂️

@ybiquitous
Copy link
Member Author

Oh, Node 12 seems to be available on AppVeyor.

appveyor/ci#2921 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants