I would recommend to run some of the CI tests on https://dev.azure.com
It's essentially the same hardware as GH Actions but gives you an extra 10 parallel jobs. This should lower the overall CI time for a pull request.
Example:
ax3l
All 4 comments
Does the azure pipeline use the same scripts as the GitHub actions? We also plan to use GitLab CI for runtime testing on GPU hardware. So we should keep the amount of CI scripts as smal as possible so we don't have to spend too much time managing the CI.
SimeonEhrig
on 13 Jul 2020
Slightly different base yaml file, as linked. But the Alpaka CI is based on bash scripts that can be executed on various CI platforms, so it's not too much to set up besides adding the compile matrix entries.
ax3l
on 13 Jul 2020
Okay, that's not so cool, because then we spread the test configuration over two files. In my opinion, we shouldn't spend time on a 3rd CI, since the integration of GitLab CI is already planned (see #967 ), and then it should be easy to add additional resources.
SimeonEhrig
on 14 Jul 2020
Sounds good, understand. Just want to mention the option :)
ax3l
on 15 Jul 2020
Related issues
mxmlnkn
路
5Comments
tdd11235813
路
4Comments
jkelling
路
4Comments
BenjaminW3
路
6Comments
ax3l
路
3Comments
Most helpful comment
Does the azure pipeline use the same scripts as the GitHub actions? We also plan to use GitLab CI for runtime testing on GPU hardware. So we should keep the amount of CI scripts as smal as possible so we don't have to spend too much time managing the CI.