I don't have a ton of visibility into the details of this error, unfortunately. But it seems that since upgrading to 2.7.0, Jenkins is now receiving triggers with the latest "Revision" hash and the correct branch (stable), but "commit notification" hashes that are from completely different branches--causing build failures. Past builds all have identical hashes under "Revision" and "commit notification", corresponding to commits in stable. Commits to stable are still triggering successful builds, but those are being swamped by the triggers coming from other branches, masquerading as triggers from stable.
I don't have a ton of visibility into the details of this error, unfortunately. But it seems that since upgrading to 2.7.0, Jenkins is now receiving triggers with the latest "Revision" hash and the correct branch (stable), but "commit notification" hashes that are from completely different branches--causing build failures. Past builds all have identical hashes under "Revision" and "commit notification", corresponding to commits in stable. Commits to stable are still triggering successful builds, but those are being swamped by the triggers coming from other branches, masquerading as triggers from stable.