-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
build server for public test visibility #412
Comments
It's public, just not well advertized! https://jenkins-node-forward.nodesource.com/ There are still some spurious failures every now and then, mostly from timing sensitive tests, but I feel confident saying it's already in better shape than the node.js CI ever was. |
Thats great, thanks. Any chance we could get the link in the readme? |
the grand plan is to have a badge at the top of the readme that shows what builds/platforms are currently passing on HEAD, when things settle down I can switch back to making that, plus proper github pull-request auto-tests, happening. |
great thanks. is there an issue for that I can reference and I'll close this? |
@thecaddy leave this one open, I'll close it when I get sorted in the iojs/build project, I still consider us in a bootstrap phase over there and there's a high level of crazy happening around this release so things will need to settle down before we get more organised |
@rvagg what's the overall status of this? |
visibility in to this is on the roadmap for @iojs/build .. WIP |
My organization is interested in switching to io.js, however, seeing a build and test suite would help give confidence in the switch and future version bumps. If the goal of the project is to move faster I think this would help quite a bit.
The text was updated successfully, but these errors were encountered: