|
|
|
|
|
by diarrhea
2172 days ago
|
|
At 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 |
|