[
https://issues.jenkins-ci.org/browse/JENKINS-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162673#comment-162673
]
Kalle Mäkelä commented on JENKINS-3265:
---------------------------------------
We were facing this problem when after Reload we wanted to trigger another
jobs. I configured the Reload Job to be run as shell script like this and this
seems to work:
curl http://localhost:80/reload
sleep 25
curl http://localhost:80/job/$Job_name/build?delay=0sec
> Reload Configuration from Disk (or POSTing config.xml) loses info on running
> builds
> -----------------------------------------------------------------------------------
>
> Key: JENKINS-3265
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3265
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Platform: PC, OS: Windows XP
> Reporter: pcampbell
> Assignee: Kohsuke Kawaguchi
>
> Executing the "Reload Configuration from Disk" while builds are running causes
> information about those builds to be lost.
> POSTing a new configuration to /job/JOBNAME/config.xml also causes the exact
> same problem. Yet editing job configuration interactively using the web form
> does not show the problem.
> I had two builds running when I reloaded configuration to pick up manual
> changes
> to one project (not running a build) config.xml file. When the browser
> refreshed, the builds were still shown as actively building in the Build
> Executor Status frame but the status indicators were no longer blinking and
> the
> project pages did not show any builds running for those projects.
> It appears that part of Hudson thought that the builds had been canceled
> because
> they were queued, blocked by themselves. The original builds appeared to
> finsish normally and then the queued builds ran. There was no record of the
> original build that had been running when the config reloaded.
> Note: If Jenkins is completely restarted, by shutting down and starting up
> the service, the missing build re-appears. (Of course, doing that each time
> is unacceptable, just trying to help focus the debugging.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
