[JIRA] [core] (JENKINS-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Ben Clifford commented on JENKINS-35666 Re: Regular 404s for running jobs that get better after job is finished. updated Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Ben Clifford updated an issue Jenkins / JENKINS-35666 Regular 404s for running jobs that get better after job is finished. Change By: Ben Clifford For some large (50%?) number of build jobs builds (across several projects) : * The job build starts. As expected: * Job build related URLs work ok. (for example, http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1/console /job/beautilytics/branch/benc-typo/1/console provides a working progressive console. * The job build appears in the LHS "build history" pane on the project page, as an in-progress job build . * The job build appears on the list of workers, as occupying a worker. * The job build is correctly linked on github as an in-progress job build .After running for several minutes, all job build related URLs for that particular build start returning 404, but the list of workers still shows the job build as occupying the worker (and provides a link which goes to the now 404-ing build page) , and the job build runs to completion successfully. Build-related URLs for other builds still work ok at this point. After the job build has run to completion, all of the job build related URLs which started 404ing work again (for example the complete console output can be seen).A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the job build , not just the progressive console.This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this project codebase/machine . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Daniel Beck commented on JENKINS-35666 Re: Regular 404s for running jobs that get better after job is finished. Project/Job is the thing you configure. Run/Build is the thing that has a start time and duration. I'm pretty sure at least some uses of "job" in the issue description should be "build", but it's not clear whether it's all of them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Ben Clifford commented on JENKINS-35666 Re: Regular 404s for running jobs that get better after job is finished. I don't understand the question. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Daniel Beck commented on JENKINS-35666 Re: Regular 404s for running jobs that get better after job is finished. Which is it in your issue description: Job/Project, or Run/Build? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Ben Clifford created an issue Jenkins / JENKINS-35666 Regular 404s for running jobs that get better after job is finished. Issue Type: Bug Assignee: Unassigned Attachments: dump.png Components: core Created: 2016/Jun/13 10:13 AM Environment: Jenkins server: Ubuntu 16.04 inside a docker container, jenkins 2.8 from pkg.jenkins-ci.org apt repo. $ java -version openjdk version "1.8.0_91" OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode) Jenkins http port is forwarded from port 2000 of docker host. Client: iceweasel 38.7.1 Priority: Major Reporter: Ben Clifford For some large (50%?) number of build jobs: The job starts.
