left project
GitLab.org / GitLab Omnibus Builder
Please see getting help page for a better place to ask your question, this repository is used to track issues with omnibus builder.
I was unable to use the GitLab repository (Note that BitBucket worked fine)...
@brewmanz dev.gitlab.org is an internal server used by GitLab Inc. and it is only accessible to employees. What are you trying to achieve?
accepted
merge request
!57
"Update rubygems and ruby to their latest security patches"
at
GitLab.org / GitLab Omnibus Builder
-
1b14810c · Merge branch 'ruby-update' into 'master'
- ... and 1 more commit. Compare 279b59a8...1b14810c
commented on
merge request !57
"Update rubygems and ruby to their latest security patches"
at
GitLab.org / GitLab Omnibus Builder
@twk3 LGTM.
opened
merge request
!57
"Update rubygems and ruby to their latest security patches"
at
GitLab.org / GitLab Omnibus Builder
-
6e4caff8 · Merge branch '2569-lock-down-nodejs' into 'master'
- ... and 1 more commit. Compare 2930b69a...6e4caff8
commented on
merge request !54
"Docker: SLES: Lock nodejs version to matching"
at
GitLab.org / GitLab Omnibus Builder
In the mean time, I will merge this manually to unblock master.
commented on
merge request !54
"Docker: SLES: Lock nodejs version to matching"
at
GitLab.org / GitLab Omnibus Builder
Debian 9 build failed again, we should switch to alternative mirror /cc @balasankarc
commented on
merge request !54
"Docker: SLES: Lock nodejs version to matching"
at
GitLab.org / GitLab Omnibus Builder
Debian 9 failed in the test stage: E: Failed to fetch http://deb.debian.org/debian/pool/main/g/gcc-defaults/g++_6.3.0-4_amd64.deb 503 Service Tem...
opened
merge request
!54
"Docker: SLES: Lock nodejs version to matching"
at
GitLab.org / GitLab Omnibus Builder