Problem: Old build can delete github results from the build which was initiated later in the pipeline.
Cause: If for eg. build nr. 28 is aborted/superseeded with build 29, but jenkins doesn't fully kill the pipeline until it times out it can happen that build br. 29 finishes first and posts results, then nr. 28 finally times out and deletes the github results from the build 29 for which we actually care.
Solution: If current build is not the latest do not delete the github results and do not post new results - we just don't care about this build results since we already know there is a newer one.
Problem:
Old build can delete github results from the build which was initiated later in the pipeline.
Cause:
If for eg. build nr. 28 is aborted/superseeded with build 29, but jenkins doesn't fully kill the pipeline until it times out it can happen that build br. 29 finishes first and posts results, then nr. 28 finally times out and deletes the github results from the build 29 for which we actually care.
Solution:
If current build is not the latest do not delete the github results and do not post new results - we just don't care about this build results since we already know there is a newer one.