4 ms·
after this downtime today. We're finally start discussing (again) to use our own Gitlab.
by haik90 6y ago
after this downtime today. We're finally start discussing (again) to use our own Gitlab.
- sschueller 6y agoI just setup auto deployment of my Android app to the app store view gitlab-ci, very cool. At this point im not sure if I should spend the time to replicate this in github actions on the copy of the repo.
- diarrhea 6y agoAt work, we have an employer-provided (some groups also have their own server/setup) GitLab instance. I work on there much more than on GitHub, and am really liking it. Everything seems neatly integrated, especially the CI/CD is nice. For all I care, GitLab can remain as it is right now. My primary fear is for it to become too bloated, trying to be all things to all people (project management, CI/CD pipeline, bugtracker, Wiki, Git repository, ...). I would be happy to find out about people's experiences rolling their own GitLab, like what pitfalls to look out for. We are on GitLab CE 13.1.3. The biggest bug plaguing us has been CI/CD failures [0] for no apparent reason; but this is solved by a retry: max: 1 when: runner_system_failure block in the CI YAML, and seems to have been fixed for new releases. [0]: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4450 https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4450
- aaomidi 6y agoI love when people suggest this and when someone asks okay who do we put in charge of having better availability than github no one has a good answer.
- Symbiote 6y agoIn your case, maybe the same people that keep microsoft.com online.
- p2detar 6y agoWe use Bitbucket on premises. It actually works great. Zero issues for the last 5 years including upgrading from one version to another.