-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.255
Git 4.4.1
Git Client 3.4.2
Platform: NonStop (itanium)
Java 1.8_25
The Git plugin picks up a change and shows the correct commit and the pipeline is launched. The job is very long running (35-ish hours), being the actual git test suite.
After the poll time expires, and Jenkins relaunches the job again reporting the same commit id - with the previous job from the day before still running. The poll configuration is (H H * * *). There are two executors in our standalone Jenkins environment.
We have been killing the second run.
This does not happen 100% of the time. It appears to be about 1 in 5.