Is there anything about CI (Contentious Integration) in Vim program?

[Marslo Jiao]

Hi,

I'm maintenance a windows-vim version (https://sourceforge.net/projects/marslosvimgvim/). However, I've got many COMPILE ERRORs recently (v7.4.399, v7.4.400, v7.4.414).

I think it's time for involving the new process. At least make compile successfully by using CI.

How do you think?

Br, Marslo

[Ken Takata]

Hi,

There is an unofficial CI project: https://github.com/vim-jp/vim-ci
It's part of Japanese Vim community (vim-jp).

Regards,
Ken Takata

[Marslo Jiao]

On Monday, 1 September 2014 20:25:49 UTC+8, Ken Takata wrote:
>
> There is an unofficial CI project: https://github.com/vim-jp/vim-ci
> It's part of Japanese Vim community (vim-jp).
>
> Regards,
> Ken Takata

That's really cool... This is the tradition CI. We can check and monitor the status of build, but we cannot control it (CI build would be triggered after the change committed).

What I mean is, if the build cannot be green (successfully), then the change will not be commit in the main branch...
Just like [gerrit](https://code.google.com/p/gerrit/) for Android.

[John Little]

Don't you mean Continuous Integration?

My thoughts...

vim is built on so many platforms, in a variety of configurations, that full CI of vim would have to be distributed, using volunteered resources; I imagine that would be difficult to organize.

I imagine we'd need a lot more tests, including platform specific rendering tests.

As it is, there are many who build vim on their own environments who pull frequently, and report problems to this list promptly.

Regards, John Little

[Marslo Jiao]

Yep, I assume that, the built issue is the easiest bug can be found. Building stuff can be finished by CI.
The CI， not the "Tradition CI" (Tradition CI means: commit code -> trigger CI [Compile -> Unit Test -> Deploy -> ...]). The tradition CI CANNOT avoid the issue-code be committed into the repository.
The CI what I mean is, when someone commit the code -> CI system is triggered -> If the job is failed -> the code will NOT be committed into the repository.

Actually, the code was committed into a TEMP-REPOSITORY for triggered the CI system, if there something wrong with the code, this commit will not be merged into the real-repository.