Class OrphanedBuildMonitorJob
- All Implemented Interfaces:
org.quartz.Job
In case we find a problematic build we cannot just remove it: 1. maybe an agent is already working on it, but just did not report in yet (agentId == null, but everything OK) 2. maybe the agent is not responsive (agentId != null, agent may or may not come back). 3. maybe 1. happened and will be followed by 2. 4. maybe the build is currently finishing, but the mechanism catches it by accident - build that is finishing properly is indistinguishable from build that is stuck in finishing state. etc.etc. In case of 1., we should give the agent some time to report in. In case of 2. or 3., we should let the AgentManager remove the agent and the build, it will do so in heartbeatTimeoutSeconds+heartbeat seconds In case of 4., we should let the build finish naturally before intervening on chain level. So, waiting heartbeatTimeoutSeconds + 2xheartbeat before taking action seems like a good idea
-
Field Summary
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionvoid
execute
(org.quartz.JobExecutionContext jobExecutionContext)
-
Field Details
-
MAP_KEY_REACTION_DELAY
- See Also:
-
-
Constructor Details
-
OrphanedBuildMonitorJob
public OrphanedBuildMonitorJob()
-
-
Method Details
-
execute
public void execute(org.quartz.JobExecutionContext jobExecutionContext) throws org.quartz.JobExecutionException - Specified by:
execute
in interfaceorg.quartz.Job
- Throws:
org.quartz.JobExecutionException
-