llvm dev - Jul 2016 - GitHub Hooks

On 2016-07-20 00:16, Mehdi Amini via llvm-dev wrote:
> Sure, "running a decent and stable web service is not a simple task”,
that’s what I’m saying.
Perhaps Travis CI could be used. They support triggering builds using an 
API [1].

[1] https://docs.travis-ci.com/user/triggering-builds

-- 
/Jacob Carlborg

> On 20 Jul 2016, at 23:09, Jacob Carlborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On 2016-07-20 00:16, Mehdi Amini via llvm-dev wrote:
> 
>> Sure, "running a decent and stable web service is not a simple
task”, that’s what I’m saying.
> 
> Perhaps Travis CI could be used. They support triggering builds using an
API [1].
> 
> [1] https://docs.travis-ci.com/user/triggering-builds
> 
I think this is great for builds and tests, but only for the environments that
Travis CI supports. If we want to do cross-platform pre-commit testing then
we're still going to need to update the build-bots somehow to be
"trigger-able" if that's the intent. If the intent is to do it
post-commit, it's not as valuable IMO.

Note that the open-source package for Travis CI ends up running on very limited
hardware [1].

Cheers

[1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments

On 2016-07-20 18:29, Dean Michael Berris via llvm-dev wrote:
> I think this is great for builds and tests, but only for the environments
that Travis CI supports. If we want to do cross-platform pre-commit testing then
we're still going to need to update the build-bots somehow to be
"trigger-able" if that's the intent. If the intent is to do it
post-commit, it's not as valuable IMO.
I was thinking on the hook to make sure that the history is linear, no 
force pushing and so on. Not ideal to use Travis CI for this but it 
could work.

-- 
/Jacob Carlborg