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

Limit concurrent build in travis #265

Closed
mcollina opened this issue Mar 15, 2017 · 12 comments
Closed

Limit concurrent build in travis #265

mcollina opened this issue Mar 15, 2017 · 12 comments

Comments

@mcollina
Copy link
Member

mcollina commented Mar 15, 2017

I think this repository would benefit a limit to the concurrent builds in Travis to 1. This might help reducing the localtunnel failures:

https://docs.travis-ci.com/user/customizing-the-build#Limiting-Concurrent-Builds

cc @calvinmetcalf @addaleax @williamkapke

@calvinmetcalf
Copy link
Contributor

calvinmetcalf commented Mar 15, 2017 via email

@calvinmetcalf
Copy link
Contributor

@Fishrock123 you've done this for us in the past

@Fishrock123
Copy link
Member

I can do it but I will probably get quite a bit of heat for doing so again if it still requests private access. I have reached out to travis to confirm whether their split perms now properly apply for organizations or not.

@mcollina
Copy link
Member Author

@Fishrock123 what will be the best approach if not? We move readable-stream to core CI infrastructure?

@Fishrock123
Copy link
Member

Probably move either the private stuff or this stuff to a new org as has been discussed before. What a mess.

@Fishrock123
Copy link
Member

Unless you really want to build for and consume core ci resources...

@mcollina
Copy link
Member Author

I'm 👍 in moving to our own org, if it's not a problem for the rest of the collaborators. It might make GitHub teams more fuzzy though.

@addaleax
Copy link
Member

Are we talking about moving readable-stream out of the nodejs github org? I am not sure I feel very positive about that. It should definitely be visible that the work here ultimately happens under the Foundation/TSC…

Other projects like node-inspect or citgm (as a project on its own) also use the Core CI infra, so there’s certainly precedent for that.

@calvinmetcalf
Copy link
Contributor

yeah I'm with @addaleax I'd prefer to only do that as a last resort

@Fishrock123
Copy link
Member

Going to email travis support. Hopefully we'll hear back.

@mcollina
Copy link
Member Author

@Fishrock123 did you hear anything back? I think we might just have to move to the foundation CI system.

@mcollina
Copy link
Member Author

This is not possible, we are moving to the Foundation CI.

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

No branches or pull requests

4 participants