-
Notifications
You must be signed in to change notification settings - Fork 5
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
Kzl 1154 ci build #320
Kzl 1154 ci build #320
Conversation
@benoitvidis We can even try node 11 or 12 no? |
949fa7d
to
154ba0d
Compare
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.
Looks OK to me but, why did you take away all the test reports?
"vuepress-plugin-container": "^2.0.1", | ||
"vuepress-validate-frontmatter": "^2.0.10", | ||
"yaml": "^1.5.1" | ||
}, | ||
"devDependencies": { | ||
"colors": "^1.3.3", |
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.
Why this?
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.
This is a dependency for the current snippet test stack.
I don't know how this happened but it was previously registered in the package-lock.json
but not in the package.json...
@Aschen , node 12 cannot be used as node-sass is not compatible with it yet. I tried node 11 and it does not change anything to the process time so I chose to stick to a LTS version. |
What does this PR do?
Adds automatic builds to documentation.
Builds will be deployed to https://docs.kuzzle.io when merged to
master
and to https://nex-docs.kuzzle.io on3-dev
.Thanks to node 10 and possibly the upgrade of vuepress, the build can be generated in a relatively acceptable time (~35mn, i.e. https://travis-ci.org/kuzzleio/documentation/jobs/541275090).
Other changes
vuepress
to 1.0.0-beta.1