Charm Needed: Gitlab-CI
Bug #1296455 reported by
Charles Butler
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juju Charms Collection |
Incomplete
|
Wishlist
|
Charles Butler | ||
Bug Description
Gitlab CI is a continuous integration server that has tight integration with Gitlab.
The current Gitlab charm does not deploy a recent enough revision of gitlab to integrate with this charm, so a few things will need to happen:
Gitlab charm needs to be updated to deploy the latest 4.x series
Gitlab CI charm needs to support both Juju deployed Gitlab installs, and non juju deployed Gitlab installations.
Gitlab-CI runners will be an additional charm (possible subordinate to consume stray resources?)
This bug will track the progress of the Gitlab-CI application
Related branches
Revision history for this message
| Charles Butler (lazypower) wrote | #1 |
| Changed in charms: | |
| status: | New → In Progress |
| description: | updated |
Revision history for this message
| Charles Butler (lazypower) wrote | #2 |
| Changed in charms: | |
| status: | In Progress → Incomplete |
Revision history for this message
| amir sanjar (asanjar) wrote | #3 |
To post a comment you must log in.
I've attached the v1 iteration of my branch for Gitlab-CI.
The installation script is in Ansible, and has a race condition with the MySQL charm not sending the required data before it attempts to make the database.
It needs Documentation, and some hook revisions. A preferred method to complete this v1 iteration would be to break apart the monolithic site.yaml file into roles that concide with each of the hooks for ease of following execution logic.