Fixed
- A probe seat now runs for the
OCTOPUS_AGENT_TIMEOUTbudget.orchestrate.sh probegave each seat the 600-secondTIMEOUTdefault even with
OCTOPUS_AGENT_TIMEOUT=1200set, and the timeout message then recommended
setting the variable that was already set. Probe seats,probe-singleand
the probe progress watchdog now use the budgetrun_agent_syncuses:
OCTOPUS_AGENT_TIMEOUT, then--timeout, then the default. A timed-out
probe seat recommendsOCTOPUS_AGENT_TIMEOUTwhen it is set. Other
background workflows still wait for their seats against--timeout, so
their seats keep that budget.
#1241,
commit 1f8d395.
Full changelog: v11.15.3...v11.15.4