gitlabhq/gitlab-ci
DEPRECATED - Please use the GitLab.com issue tracker observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 8
- Longevity 100
Flags: archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5075
- days_rel: n/a
- days_push: 3763
- n_releases_24m: 0
Adoption not part of the score
1445 stars · 310 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
GitLab CI was an open-source continuous integration server written in Ruby. It was integrated into GitLab 8.0, and this repository now only serves as a migration tool for pre-8.0 CI servers.
Use cases
- migrate data from a standalone GitLab CI server into GitLab 8.0
- run a self-hosted continuous integration server for legacy GitLab setups
- understand the history of GitLab's CI integration
When to choose
- you are migrating an old pre-8.0 GitLab CI installation into modern GitLab
- you need to reference the original standalone CI server code
When to avoid
- you want a CI/CD system for new projects - use built-in GitLab CI/CD instead
- you need an actively maintained integration server
Facets
application · maturity abandoned
ci-cd testing developer-tools self-hosted ruby continuous-integration deprecated gitlab migration-tool devops web-server
2 sources
- readme: https://github.com/gitlabhq/gitlab-ci · fetched 2026-08-28 · 27bec0a7eee2
- homepage: https://gitlab.com/gitlab-org/gitlab-ce/issues · fetched 2026-08-29 · 1a538c453cd6
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| gitlabhq/gitlab-ci | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="gitlabhq/gitlab-ci")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem