CI build pipeline does not complete (individual builds all completed)
### Summary
Current version is the 8.12.3 pulled from the [docker image](https://hub.docker.com/r/sameersbn/gitlab/).
The CI build does not complete. The individual builds and all stages complete, we get the green `passed` icon; however the build itself stays in `running`
This issue persists even after restarting the gitlab server.
### Steps to reproduce
Not sure. I ran into this bug at some point (where the step I took was the ordinary. Updated the test script, then commited and pushed.
This build has been stuck, and the next build after that is also stuck (merge request to the master branch).
### Expected behavior
As the internal jobs of the build all succeed, the build itself should complete.
### Actual behavior
Internal jobs are all `passed` but the jobs state stays `running`.
### Relevant logs and/or screenshots
Refer to screenshot above.
### Output of checks
#### Results of GitLab application Check
```
Checking GitLab Shell ...
GitLab Shell version >= 3.6.1 ? ... OK (3.6.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
3/2 ... ok
2/3 ... ok
3/4 ... ok
2/5 ... ok
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /home/git/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder yet)
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...
3/2 ... yes
2/3 ... yes
3/4 ... yes
2/5 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.1)
Your git bin path is "/usr/bin/git"
Git version >= 2.7.3 ? ... yes (2.10.0)
Active users: 3
Checking GitLab ... Finished
```
#### Results of GitLab environment info
```
System information
System: Ubuntu 14.04
Current User: git
Using RVM: no
Ruby Version: 2.3.1p112
Gem Version: 2.5.1
Bundler Version:1.13.2
Rake Version: 10.5.0
Sidekiq Version:4.1.4
GitLab information
Version: 8.12.3
Revision: 467e1ca
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: https://cabackup.kaist.ac.kr:19443
HTTP Clone URL: https://cabackup.kaist.ac.kr:19443/some-group/some-project.git
SSH Clone URL: ssh://git@cabackup.kaist.ac.kr:19022/some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 3.6.1
Repository storage paths:
- default: /home/git/data/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/bin/git
```
### Possible fixes
Not sure of any workarounds
issue