Usage with Gitlab CI

Support
#1

Hi,

I’m trying to use Bors with GitHub + GitLab CI, and I’m running into a status name issue. GitLab CI doesn’t have consistent status names, so when using the trying/staging set-up it pushes updates to respectively ci/gitlab/trying and ci/gitlab/staging. I’m using the latter in bors.toml right now to get bors r+ to work, but as a result I get time-outs when doing bors try.

Is there a way to work around this? GitLab is going to add consistent status names, but those will be tied to the hostname of the system running CI (ie. ci/gitlab/host-name) and I’d prefer not to rely on that.

Repo at https://github.com/JuliaGPU/CuArrays.jl, example time-out https://github.com/JuliaGPU/CuArrays.jl/pull/181, but r+ works https://github.com/JuliaGPU/CuArrays.jl/pull/185.

#2

There doesn’t seem to be a nice way to do that in Bors, as it currently exists.

The best way to fix it would probably be to allow globbing in the status lines. For example, ci/gitlab/* would match anything that starts with ci/gitlab/.

Anybody around who’d want to try implementing that? I’d be happy to help walk you through any info you’d need to do it.

#3

OK, thanks. I don’t really have the time to look into this myself (and lack the Rust experience to do so efficiently), so I’ll probably wait for the GitLab workaround instead.
Should I open an issue about this?

#4

https://github.com/bors-ng/bors-ng/issues/539

#5

@maleadt

Will this work?

https://github.com/bors-ng/bors-ng/pull/547

https://github.com/bors-ng/bors-ng.github.io/commit/203a121971f127ab7277dc8e60d0aee60fd2d368

#6

Oh great! Need to trial some more, but definitely looks like it’s working as expected. Thanks!

1 Like