Folks;
we're just moving into gitlab CI for doing build and assembly for our
applications, and I am ended up with what seems a more complex question:
Most of our applications (server sided as well as JavaFX client stuff) are
maven based Java projects consisting of various interdependent module
Folks;
we used to set up our gitlab instance internally on a machine that, initially,
was just exposed as
"git" so all the repositories, the links in activation mails, ... point to
"http://git/";. How can I
change this afterwards to some more sane (and publicly exposable) value?
Browsing the do
Folks;
I've been experiencing a *rather* strange behaviour with our gitlab
installation. System runs behind
an apache2 reverse proxy exposing HTTPS. I do have an external user who has
restricted access to
various projects. He entered his (valid) credentials and wasn't allowed access
to the desi
Am Mittwoch, den 23.11.2016, 09:21 -0800 schrieb Aleksey Tsalolikhin:
> Did you reconfigure GitLab after updating gitlab.rb?
>
Nope. :| That obviously did it - thanks a bunch. :)
Cheers,
Kristian
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To u
Am Montag, den 05.12.2016, 07:28 -0800 schrieb Aleksey Tsalolikhin:
> Is it a public project that your user checked out?
> Gitlab is a wrapper around git (in rough times). You don't see a git user in
> GitLab UI because
> it's at the Git level underneath GitLab.
Layer 8 issue - or, better, error
Folks;
we're using gitlab all along with maven and some heavier Java/Vaadin
projects which even on more potent infrastructure take quite a while to
really build. Right now, with gitlab-ci configuration and configured
runners, the build happens after each commit to a project which is quite
heavy.
Hi *;
and thanks for your feedback and help on that. Gonna pass this on to the
team, seems this solves our problem. Great to see it's possible like
that. :)
Thanks again and all the best,
Kristian
Am Dienstag, den 28.02.2017, 09:48 +0100 schrieb Magnus Therning:
> Aleksey Tsalolikhin writes:
Folks;
we're using gitlab CE set to be accessed through an apache2 reverse
proxy that does HTTPS and has a valid certificate. Is there some way to
set up gitlab so that any links (repository URLs, ...) in gitlab are
exposed as "https" even without making gitlab expose HTTPS directly?
TIA and all t
Am Donnerstag, den 04.05.2017, 03:19 -0700 schrieb Aleksey Tsalolikhin:
> Not that I've seen. Why not just turn on HTTPS in GitLab?
>
Hmmm... That would work if gitlab by then still works in HTTP and I
still can do reverse proxy to the HTTP port. Would that be possible?
Cheers,
Kristian
--
You
