-
Notifications
You must be signed in to change notification settings - Fork 293
chore(ci): get CI working again #462
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
chore(ci): get CI working again #462
Conversation
Node 6.x has been EOL since April 2019, and Node 8.x becaome EOL in Dec 2019. This pushes the CI environment to use an Active LTS version of Node. Refs: https://github.com/nodejs/Release Signed-off-by: Mike Fiedler <[email protected]>
Uncertain of why this is currently failing - it's possible the global version of node in the `circleci/classic` image is incompatible - that should be investigated independently. In the meantime, the rest of CI isn't being run. Signed-off-by: Mike Fiedler <[email protected]>
These un-linted changes have crept in due to lack of CI making it here. Signed-off-by: Mike Fiedler <[email protected]>
Appveyor testing is failing due to a warning during installation of the `serverless` package, since the `fsevents` dependency is targeting the `darwin` architecture. Signed-off-by: Mike Fiedler <[email protected]>
The test was introduced to test the behavior of a particular pre-release version of poetry, prior to version 1.0.0 being released. It has since been released on Dec 12, 2019. Refs: https://python-poetry.org/blog/announcing-poetry-1-0-0.html Refs: serverless#395 Signed-off-by: Mike Fiedler <[email protected]>
ecef22b
to
ca2bfc1
Compare
Update to run against Python 3.x instead of EOL 2.x Signed-off-by: Mike Fiedler <[email protected]>
Here's the good news: CircleCI is passing now! So a couple of things we could do here: a. remove appveyor as a testing target for now - how well do we trust the Windows/Python/Node/Docker setup? |
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've gone over this per commit, everything makes sense. I'm going to opt for c. I'll bang my head against appveyor, may as well try to figure it out.
Good lord, I didn't realize we were building python on Circle. |
Yeah, we can improve! |
This started as a simple version update, but I found more things that needed fixing before we can get back to a full CI run again.
Please review by commit.
Signed-off-by: Mike Fiedler [email protected]