Looking at the contribution guidlines, travisCI would be a good idea

[anadon]

Looking here: https://github.com/intel/compute-runtime/blob/master/documentation/RELEASES.md

it seems like adding travisCI integration would make like easier.

[PiotrRozenfeld]

We agree with you, we are already looking into integration with Travis CI (or alternative).
Will keep the issue open until we either have initial integration deployed, or at least more elaborate plan added to FAQ.md

[anadon]

There are a few other continuous integration tools which you may be interested in then, like Appvoyer, codecov.io and coveralls.io .

[JacekDanecki]

I've looked at your proposal, but I've selected 3 CI systems, and have been testing them:

• Travis: https://travis-ci.org/JacekDanecki/compute-runtime
• Shippable: https://app.shippable.com/github/JacekDanecki/compute-runtime/dashboard
• Semaphore: https://semaphoreci.com/jacekdanecki/compute-runtime
  At this moment 3 OS's are tested: Ubuntu 16.04, Ubuntu 18.04, Arch with all compilers we support now. Fedora is in queue.

[anadon]

Cool! With Arch, Ubuntu, and Fedora the three large families of distros appears to be represented. Over time, it would still be good to expand on this but not as high of a priority.

I will bring up appvoyer again because then you could do the same with Windows which would help save time on maintaining multiple highly similar code bases and allow them to be the same code base. That in turn should free up developer resources to actually work on the parts you all care about more :)

[anadon]

Checking out the tests, I will suggest you add tests for gcc major versions 4, 6, 7, and 8 where possible. Clang from my experience is a tad more consistent between major versions. RHEL 6 and 7 rely on gcc 4, ubuntu 18.04 uses gcc 7, and arch recently switched to gcc 8. It looks like gcc 8 is going to be one of the longer lived versions due to the more recent and mostly stable support of C++17.

[JacekDanecki]

At this moment we don't support Neo compilation under Windows using open source components.
In case of tested compilers to compile Neo, at this moment we use gcc: 5, 6, 7 and clang 4, 5 with different minor versions. Compilation with gcc 8 and clang 6 fails, and is on our todo list.

[grmat]

Compilation with gcc 8 and clang 6 fails, and is on our todo list.

@JacekDanecki Don't you want to open a separate issue for this, so it can easily tracked?

I was interested in neo and created a PKGBUILD, the standard format shell script for automated package builds for Arch Linux. Right now, I'm also using gcc54, as that's already in the official repos, but it's not usual and has some kind of exceptional position because it's required for CUDA and might be dropped out of the repos again.

I also considered pushing it into the AUR (Arch User Repository), but have second thoughts after seeing your recent effort in automated builds. Do you consider officially supporting Arch Linux? Do you consider updating your CI build scripts with a PKGBUILD instead of a bunch of manually created build scripts? As you can see, the syntax is pretty simple, easier to maintain and it creates a suitable package which might land in the official repos.

[anadon]

@grmat As mentioned above

At this moment 3 OS's are tested: Ubuntu 16.04, Ubuntu 18.04, Arch with all compilers we support now. Fedora is in queue.

Also, you should be using the gcc base package for Arch, not gcc54. gcc will always be there and maintained, but gcc54 is for compatibility purposes.

Arch may work, but should not be officially supported since it is a rolling distribution and at regular times breaks itself.

@JacekDanecki There is a good suggestion here of building and testing off of a PKGBUILD. There are some good practices there which will help packaging for other distributions in general, and make sure everything is being done in a way which conforms with many best practices.

[grmat]

Also, you should be using the gcc base package for Arch, not gcc54. gcc will always be there and maintained, but gcc54 is for compatibility purposes.

You basically just repeated what I already wrote. The sole reason 5.4 is used right now is that it doesn't build with gcc8, hence I was asking for the status.

Arch may work, but should not be officially supported since it is a rolling distribution and at regular times breaks itself.

It does not break itself. Software breaks, as you can see right here with newer compiler versions. That's why packages are maintained. An up-to-date distribution doesn't break itself.

[JacekDanecki]

Current CI scripts build Neo using IGC binaries from the latest release. This is why I did not create PKGBUILD as you've prepared.
At this moment full build on Travis is not possible, because of build time limits.
You don't need to clone gmock/gtest anymore as they are included in third_party/gtest directory.
Fixes to compile Neo with gcc-8 have been just merged, and Travis builds with gcc-8 are tested here: https://travis-ci.org/JacekDanecki/compute-runtime. Note: Fixes for IGC are still pending.
See #46 for information about supporting further distros.

[JacekDanecki]

I'll close this issue, as initial integration with Travis was implemented and deployed. I'm still working on tuning it, so you can expect more changes soon. Please reopen it when needed or file new issue.