Build job details no longer refreshes when build finishes
Summary
When viewing the build output of a job that is currently running, while new output is streamed, the site will no longer update when the job finishes.
Steps to reproduce
- Have a project with GitLab CI set up.
- Trigger a build by pushing to it.
- Find the running build job and click on it to get the build output.
- Scroll down. Notice that new build output is added to the page automatically every second or so.
- Wait for the build to finish.
What is the current bug behavior?
When the build finishes, the page stops updating. The build is still shown as running. The latest batch of build output (generated between the last update and the build finishing) is not shown. When refreshing the page, the full build output appears, and the job is shown as completed.
What is the expected correct behavior?
The page should update automatically – either by simply refreshing, or by the status being updated inline. (This is a regression: Previously, a page reload was triggered automatically when the build finished.)
Output of checks
Results of GitLab environment info
System information
System:
Current User: git
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version: 2.6.6
Bundler Version:1.13.7
Rake Version: 10.5.0
Redis Version: 3.2.5
Git Version: 2.10.2
Sidekiq Version:4.2.7
GitLab information
Version: 9.0.0
Revision: cf020e6
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://■■■■■.■■.■■■■■■■■■■■■.■■/gitlab
HTTP Clone URL: https://■■■■■.■■.■■■■■■■■■■■■.■■/gitlab/some-group/some-project.git
SSH Clone URL: ssh://git@■■■■■.■■.■■■■■■■■■■■■.■■:2222/some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 5.0.0
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/
Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Checking GitLab Shell ...
GitLab Shell version >= 5.0.0 ? ... OK (5.0.0)
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: ...
2/1 ... ok
5/2 ... ok
1/3 ... ok
1/5 ... ok
15/6 ... ok
15/7 ... ok
15/8 ... ok
2/10 ... ok
5/11 ... ok
7/12 ... ok
3/13 ... ok
1/14 ... ok
1/15 ... ok
2/16 ... ok
3/17 ... ok
3/18 ... ok
12/19 ... ok
15/20 ... repository is empty
15/21 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.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? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
projects have namespace: ...
2/1 ... yes
5/2 ... yes
1/3 ... yes
1/5 ... yes
15/6 ... yes
15/7 ... yes
15/8 ... yes
2/10 ... yes
5/11 ... yes
7/12 ... yes
3/13 ... yes
1/14 ... yes
1/15 ... yes
2/16 ... yes
3/17 ... yes
3/18 ... yes
12/19 ... yes
15/20 ... yes
15/21 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.10.2)
Active users: 13
Checking GitLab ... Finished
Additional details
I'm running a subfolder install – maybe this is related? No errors are logged in the browser console when this happens.