Jenkins build web UI inaccessible while build is executing

28 views
Skip to first unread message

Alan Evangelista

unread,
Mar 28, 2016, 4:40:44 PM3/28/16
to jenkins...@googlegroups.com
Hi.

I have a job configured in Jenkins. Job's latest build # is ~ 10000. When I execute the job via
Jenkins API, the new build does not appear in the job UI in Jenkins. The new build appears in the
build executor status pane in Jenkins home page, but if I click in the build link
(http://<jenkins_server>/job/<job_name>/<build_number>/), I get a 404 error. I also cannot find
the build using Jenkins API (http://<jenkins_server>/job/<job_name>/<build_number>/api/json/).
When the build completes, the link to it in web UI becomes accessible and it is found via Jenkins
API.

Strangely, this has only started to happen recently in my Jenkins server. I am not sure if is is related,
but also recently I started to receive "Please wait while Jenkins is getting ready to work" messages in
Jenkins web UI, like if Jenkins was being restarted often.

I use Jenkins version 1.629.

Has anyone faced this problem before?


Regards,
Alan Evangelista

Alan Evangelista

unread,
Mar 29, 2016, 6:32:30 PM3/29/16
to jenkins...@googlegroups.com

I have a job configured in Jenkins. Job's latest build # is ~ 10000. When I execute the job via
Jenkins API, the new build does not appear in the job UI in Jenkins. The new build appears in the
build executor status pane in Jenkins home page, but if I click in the build link
(http://<jenkins_server>/job/<job_name>/<build_number>/), I get a 404 error. I also cannot find
the build using Jenkins API (http://<jenkins_server>/job/<job_name>/<build_number>/api/json/).
When the build completes, the link to it in web UI becomes accessible and it is found via Jenkins
API.

Strangely, this has only started to happen recently in my Jenkins server. I am not sure if is is related,
but also recently I started to receive "Please wait while Jenkins is getting ready to work" messages in
Jenkins web UI, like if Jenkins was being restarted often.


FYI I had a daemon running which incorrectly reloaded Jenkins configuration from the disk every minute.
When I fixed this bug, the issue stopped.


Regards,
Alan Evangelista

Reply all
Reply to author
Forward
0 new messages