Re: [DISCUSS] Ongoing Travis CI service degradation

[Sutou Kouhei <ko...@clear-code.com>]

Hi,

> GitLab-CI integrates structured artifacts (like which
> tests pass and their output [1] and changes to continuous metrics like
> performance [2])

I didn't know it.

Our CI failures aren't just only test failures. We have lint
failures, build failures (they may be occurred by external
dependencies) and so on. So our needs for the structured
artifacts feature may be limited.


Thanks,
--
kou

In <87...@jedbrown.org>
  "Re: [DISCUSS] Ongoing Travis CI service degradation" on Sat, 29 Jun 2019 21:02:41 -0600,
  Jed Brown <je...@jedbrown.org> wrote:

> Sutou Kouhei <ko...@clear-code.com> writes:
> 
>> How about creating a mirror repository on
>> https://gitlab.com/ only to run CI jobs?
>>
>> This is an idea that is described in
>> https://issues.apache.org/jira/browse/ARROW-5673 .
>>
>> GitLab CI can attach external workers. So we can increase CI
>> capacity by adding our new workers. GitLab also provides
>> Docker registry. It means that we can cache built Docker
>> images for our CI. It will reduce CI time.
> 
> I have some experience with GitLab-CI.  The gitlab-runner is great and
> easy to deploy.  GitLab-CI integrates structured artifacts (like which
> tests pass and their output [1] and changes to continuous metrics like
> performance [2]) very nicely into GitLab Merge Requests, but when you
> connect to an external repository (GitHub, etc.), it only reports
> pass/fail and you can't access the structured artifacts [3], only the
> console logs and compressed archives of artifacts if you use that
> feature.
> 
> If you're happy with clicking through to console logs in case a pipeline
> fails (the Travis model), then GitLab-CI is easy to use and will serve
> your purposes.  If you really want the structured features, then I'd
> encourage you to mention that in [3].
> 
> [1] https://docs.gitlab.com/ee/ci/junit_test_reports.html#how-it-works
> [2] https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html#how-it-works
> [3] https://gitlab.com/gitlab-org/gitlab-ce/issues/60158