Nevermind my ramblings - it was a case of PEBKAC.
Issues was caused by conflict between DNS and /etc/hosts - I was using the
correct Gitlab server (via my local /etc/hosts file) while other users were
using DNS which was pointing to staging/testing Gitlab server.
Regards,
ak.
On Thursday, 28 A
Is there a way to have GitLab manage more than a single git-data dir?
A workaround is to run multiple VMs each with a fully independant GitLab
instance.
Are there any other ideas?
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from
Am 28.04.2016 um 11:56 schrieb Razvan Crainea:
>
>
> On Thursday, April 28, 2016 at 12:29:29 AM UTC+3, Urs Liska wrote:
>
> Hi Maximilian,
>
> thanks for considering my issue.
>
> Am 27.04.2016 um 20:13 schrieb 'Maximilian Kindshofer' via GitLab:
> >
> > Am Montag, 25. April 2
Hello, I'm getting following error for artifacts in .gitlab-ci.yml
ERROR: Uploading artifacts to coordinator... too large archive id=38 token=
kfvs6A2i
FATAL: Too large ERROR: Build failed: exit code 1
nginx setting for client_max_body_size is 0.
--
You received this message because you are
Something similar was happening yesterday to me with wiki pages on
gitlab.com: Error 500 when creating a new page.
https://groups.google.com/d/msg/gitlabhq/WuVDVQHG5rc/Z0nh0uR1BAAJ
Today it is still happening.
On Thursday, April 28, 2016 at 11:56:34 AM UTC+2, Razvan Crainea wrote:
>
>
>
> On Th
On Thursday, April 28, 2016 at 12:29:29 AM UTC+3, Urs Liska wrote:
>
> Hi Maximilian,
>
> thanks for considering my issue.
>
> Am 27.04.2016 um 20:13 schrieb 'Maximilian Kindshofer' via GitLab:
> >
> > Am Montag, 25. April 2016 11:14:04 UTC+2 schrieb Urs Liska:
> >
> > I could resolve t
