Minor If 'tick' is enabled on the credential and a reconcile fails due to network problems, the reconcile is restarted but the old thread is left running in the background. This causes 'tick' messages to be seen past the end of the job and build workspaces can be in an inconsistent state.
Note - Have not been able to reproduce in the lab (yet). Logging this for visibility.
Example console extract:
03:54:52 (p4):cmd:... p4 reconcile -f -m -w C:\A\B/...
03:55:02 ...tick...
03:55:12 ...tick...
03:55:22 ...tick...
---cut---
04:03:02 ...tick...
04:03:06 P4 Task: attempt: 1
04:03:09
04:03:09 P4 Task: reverting all pending and shelved revisions.
04:03:09 ...tick...
04:03:09 (p4):cmd:... p4 revert C:\A\B/...
---cut---
04:13:22 ...tick...
04:13:23 (p4):stop:18
04:13:23 duration: 3m 29s
04:13:23
04:13:23 P4 Task: syncing files at change: 150
04:13:23 (p4):cmd:... p4 sync --parallel=threads=4,min=1,minsize=1024 -q C:\A\B/...@150
04:13:24 ...tick...
04:13:29 P4: saving built changes.
04:13:46 [Pipeline] pwsh
04:13:36 ...tick...
04:13:39 ...tick...
04:13:39 ...tick...
04:13:40 ...tick...
04:13:42 ...tick...
04:13:47 [Pipeline] }
---cut---
05:21:01 ...tick...
05:21:02 ...tick...
05:21:04 ...tick...
05:21:10 Uploaded 1 artifact(s) to https://MY-URL/artifacts/
05:21:10 [Pipeline] }
The 'tick' message can be seen long after the last P4 command has run suggesting the thread is still running in the background.
I do not know if 'tick' being enabled highlights the problem or is part of the cause.
