I think there is an aspect which I didn't mention of "Who do you trust with your code?" and GitHub has done well to earn the trust of lots of great companies, but I can certainly see IT managers getting a bit ancy at adding another point of confidentiality failure by looping in Travis as well.
Maybe "Enterprise" accounts could have VMs with FDE; Travis gives them a bare image that's then encrypted w/ a user-provided key, so (barring a hostile attack on the host's memory) only the user has access to their data.
Though the same users that want such a thing are likely also running (locally hosted) GitHub Enterprise, it'd make more sense to provide a similar option for Travis.
Comments
Oh, neat!
I think there is an aspect which I didn't mention of "Who do you trust with your code?" and GitHub has done well to earn the trust of lots of great companies, but I can certainly see IT managers getting a bit ancy at adding another point of confidentiality failure by looping in Travis as well.
Maybe "Enterprise" accounts could have VMs with FDE; Travis gives them a bare image that's then encrypted w/ a user-provided key, so (barring a hostile attack on the host's memory) only the user has access to their data.
Though the same users that want such a thing are likely also running (locally hosted) GitHub Enterprise, it'd make more sense to provide a similar option for Travis.