[SAC] gitlab-ci hitting too hard ?

Committees SAC mailing list
1

I noticed an incoming POST every 2 seconds from a gitlab-ci runner
service from the experimental GitLab host to the GitLab service
(spotted in Apache logs, which acts as a reverse proxy).

Björn is that something you can stop, until the CI actually does
something useful ? It's currently broken anyway, as reported in
https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues/12

Mateusz: I've added you in Cc here as I had the impression you wanted
to try at using GitLab for OSGeo, please see the currently open
issues here: https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues

--strk;

2

I will have a look. Despite apparent minor interest in GitLab,I want to at least test tickets export from Trac to GitLab

···

On 5 Apr 2017 10:54 a.m., “Sandro Santilli” <strk@kbt.io> wrote:

I noticed an incoming POST every 2 seconds from a gitlab-ci runner
service from the experimental GitLab host to the GitLab service
(spotted in Apache logs, which acts as a reverse proxy).

Björn is that something you can stop, until the CI actually does
something useful ? It’s currently broken anyway, as reported in
https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues/12

Mateusz: I’ve added you in Cc here as I had the impression you wanted
to try at using GitLab for OSGeo, please see the currently open
issues here: https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues

–strk;

3

Responded in rush from my mobile and just realised "I will have a
look" might lead to misunderstanding.
I aim to have a look at the Trac to GitLib issues migration only.
I'm not interested in GitLab admin or maintenance.

Mateusz

On 5 April 2017 at 14:38, Mateusz Loskot <mateusz@loskot.net> wrote:

I will have a look. Despite apparent minor interest in GitLab,I want to at
least test tickets export from Trac to GitLab

On 5 Apr 2017 10:54 a.m., "Sandro Santilli" <strk@kbt.io> wrote:

I noticed an incoming POST every 2 seconds from a gitlab-ci runner
service from the experimental GitLab host to the GitLab service
(spotted in Apache logs, which acts as a reverse proxy).

Björn is that something you can stop, until the CI actually does
something useful ? It's currently broken anyway, as reported in
https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues/12

Mateusz: I've added you in Cc here as I had the impression you wanted
to try at using GitLab for OSGeo, please see the currently open
issues here: https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues

--strk;

--
Mateusz Loskot, http://mateusz.loskot.net

4

Understood :slight_smile: Feedback on usage is appreciated.

/Björn

···

2017-04-05 21:26 GMT+02:00 Mateusz Loskot <mateusz@loskot.net>:

Responded in rush from my mobile and just realised “I will have a
look” might lead to misunderstanding.
I aim to have a look at the Trac to GitLib issues migration only.
I’m not interested in GitLab admin or maintenance.

Mateusz

On 5 April 2017 at 14:38, Mateusz Loskot <mateusz@loskot.net> wrote:

I will have a look. Despite apparent minor interest in GitLab,I want to at
least test tickets export from Trac to GitLab

On 5 Apr 2017 10:54 a.m., “Sandro Santilli” <strk@kbt.io> wrote:

I noticed an incoming POST every 2 seconds from a gitlab-ci runner
service from the experimental GitLab host to the GitLab service
(spotted in Apache logs, which acts as a reverse proxy).

Björn is that something you can stop, until the CI actually does
something useful ? It’s currently broken anyway, as reported in
https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues/12

Mateusz: I’ve added you in Cc here as I had the impression you wanted
to try at using GitLab for OSGeo, please see the currently open
issues here: https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues

–strk;

–
Mateusz Loskot, http://mateusz.loskot.net

5

I have paused the runner until further notice.

/Björn

···

2017-04-05 10:54 GMT+02:00 Sandro Santilli <strk@kbt.io>:

I noticed an incoming POST every 2 seconds from a gitlab-ci runner
service from the experimental GitLab host to the GitLab service
(spotted in Apache logs, which acts as a reverse proxy).

Björn is that something you can stop, until the CI actually does
something useful ? It’s currently broken anyway, as reported in
https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues/12

Mateusz: I’ve added you in Cc here as I had the impression you wanted
to try at using GitLab for OSGeo, please see the currently open
issues here: https://git.osgeo.org/gitlab/gitlab/osgeo-gitlab/issues

–strk;