Repository navigation
Setup Travis CI #57
Description
Since the nodejs org doesn't allow 3rd party GH apps org wide access, we have to get Travis setup in a very weird way to get our PRs tested with Travis.
@Fishrock123 as you're the champion of semi-setup for Travis, you willing to help me on this?
Metadata
Metadata
Assignees
Labels
No labels
Activity
Fishrock123 commentedon Aug 5, 2016
oh, right
phillipj commentedon Aug 8, 2016
FYI for others, this is currently blocked due to security concerns mentioned in nodejs/help#243.
jbergstroem commentedon Aug 8, 2016
Also, we're currently experimenting with using our own Jenkins environment together with nvm to keep track of Node versions.
Trott commentedon Jun 8, 2018
Done in nodejs/node#21059.
phillipj commentedon Jun 8, 2018
If I recall correctly, this issue was created to enable Travis in this repo. We've got lots of tests on the bot that would be great to have run as part of PRs, without us having to double check the branches before merging them 😞
phillipj commentedon Jun 22, 2018
This has finally been resolved as we've transitioned from Travis CI as a GitHub service & polling hacks via the github-bot, to Travis CI GitHub app allowing us to provide Travis the access it needs per repo, not across the entire organisation.
Refs #183