[Bugs] [Bug 1428047] Require a Jenkins job to validate Change-ID on commits to branches in glusterfs repository

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1428047



--- Comment #17 from Shyamsundar <srangana at redhat.com> ---
Here is an easy example that is in my mind:

- The rfc.sh already does this job and let's the committer know that the change
ID is not present in master
(https://github.com/gluster/glusterfs/blob/master/rfc.sh#L70)

- The same check needs to be performed, and a message posted to the patch, that
the Change-ID is either inconsistent or missing

- The job need not vote, as at times having different change IDs or not finding
a change ID on master is a valid case (release notes, release specific patches
are examples where the change ID in the branch will not be found in master)

The intent of the job is simply to remind reviewers that the change ID is
different and we may want to cross check that to ensure that it is genuine and
not an error by the committer.

Does the above help? Or, do you need more here?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=opypL0DzRs&a=cc_unsubscribe