[Help Wanted] Build numbers reported in Github correspond to wrong builds and in completely different pipelines

[jemishdave]

We have team members who have reported an issue few times where the CI Status message in the Gihub Pull Request corresponds to a wrong build number for a wrong job in a completely seperate pipeline. Example here shows 3 images. First image shows two consecutive commits a day apart Second and third images are screenshots for their respective CI builds As shown in the image, we can see the commits and corresponding builds which are pointing to seperate jobs in concourse. Need your help in identifying the root cause of this issue.

[jtarchie]

@jemishdave, I am not following along what your issue is.

1. Are you showing that the status (success/failure) is being applied to the incorrect SHA?
2. Are you showing that the build number doesn't appear somewhere?
3. Are you showing that the build link goes to an incorrect place?

[jemishdave]

Updates below:

Are you showing that the status (success/failure) is being applied to the incorrect SHA? JD: This might be true. Not sure Are you showing that the build number doesn't appear somewhere? JD: The build number does appear Are you showing that the build link goes to an incorrect place? JD: Yes, this is the case exactly. The Pull Request Resource is looking for changes to MASTER branch in one repo. The correct job/task also gets triggered. However, when status is reported back to Github the build link refers to another build ( which normally belongs to a totally different pipeline )

[john681611]

Github is getting failed status messages from builds that aren't linked to the repo or pr. We are running concourse v3.8.0 Your examples don't show sending pending messages do we need to?

Links provided are along the lines of www.concourseSite.com/builds/2819

not the links found by navigation usually www.concourseSite.com/teams/'team'/pipelines/'pipeline'/jobs/'job'/builds/318