[Gluster-infra] [Bug 1428032] New: Update WorkerAnt to post to a github issue as soon as a patch is posted against the same
https://bugzilla.redhat.com/show_bug.cgi?id=1428032
Bug ID: 1428032
Summary: Update WorkerAnt to post to a github issue as soon as
a patch is posted against the same
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: nig...@redhat.com
Reporter: srang...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
Gluster intends to move to github to track features being delivered against the
code base.
Read the announcement here:
http://lists.gluster.org/pipermail/gluster-devel/2017-February/052203.html
Specifics of the github process here: https://hackmd.io/s/BkgH8sdtg#
Towards the above the following change is requested:
Update WorkerAnt to post to a github issue as soon as a patch is posted against
the same
Detect patch posted against an issue using the "{Fixes|Updates} #n" or
"{Fixes|Updates} gluster/glusterfs#n" in the commit message
Change:
https://github.com/gluster/gerrit-hooks/blob/master/patchset-created to update
the issue to reflect that a patch is posted against it (just like bugzilla is
updated by WorkerAnt)
This is required, so that we do not have to wait till a merge of the
commit, for the details to appear against the issue
This needs to change to pick up commits posted against glusterfs,
glusterfs-specs, as these are controlled via gerrit
For glusterdocs however, only when the documentation PR is submitted and
accepted, will the issue be updated (which is fine)
WorkerAnt is used to state what should change, but this request may need
another bot or some other means of achieving the same. Hence, do not consider
WorkerAnt as the final entity that needs to change.
--
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=bBxIPvO9fI&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1428034] New: Enable gerrit to convert github issue reference as a hyperlink
https://bugzilla.redhat.com/show_bug.cgi?id=1428034 Bug ID: 1428034 Summary: Enable gerrit to convert github issue reference as a hyperlink Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: nig...@redhat.com Reporter: srang...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Gluster intends to move to github to track features being delivered against the code base. Read the announcement here: http://lists.gluster.org/pipermail/gluster-devel/2017-February/052203.html Specifics of the github process here: https://hackmd.io/s/BkgH8sdtg# Towards the above the following change is requested: Like gerrit provides in the BUG value a link to bugzilla, is it possible to provide a link to an github issue when that is referenced in the commit message? That would be quite nice, instead of having to form the URL every time Example from the go gerrit site: https://go-review.googlesource.com/#/c/37148/ -- 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=6s3HtgC22R&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1428036] New: Update rfc.sh to check/ request issue # when a commit is an “rfc”
https://bugzilla.redhat.com/show_bug.cgi?id=1428036 Bug ID: 1428036 Summary: Update rfc.sh to check/request issue # when a commit is an “rfc” Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: nig...@redhat.com Reporter: srang...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Gluster intends to move to github to track features being delivered against the code base. Read the announcement here: http://lists.gluster.org/pipermail/gluster-devel/2017-February/052203.html Specifics of the github process here: https://hackmd.io/s/BkgH8sdtg# Towards the above the following change is requested: Update rfc.sh to check/request issue # when a commit is an “rfc”: Change: https://github.com/gluster/glusterfs/blob/master/rfc.sh This is more a helping hand for the process, when a bug ID is not entered, it would be helpful to check if the commit message has a Fixes or Updates issue# comment, else prompt and edit the commit message accordingly The prompt can just be for an issue number, and not specifically "Updates" or "Fixes", just to keep it light. If the commit really is the last fix the submitter/reviewer should be able to handle the request for the appropriate keyword. For glusterfs-specs, we use git-review instead of rfc.sh, so a test needs to be enforced somewhere in that workflow for issue# presence (even reviewers can request for the same if it is missing), if possible lets automate it, else we will have to depend on reviewers -- 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=ZVFvTHSRm8&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1428047] New: Require a Jenkins job to validate Change-ID on commits to branches in glusterfs repository
https://bugzilla.redhat.com/show_bug.cgi?id=1428047 Bug ID: 1428047 Summary: Require a Jenkins job to validate Change-ID on commits to branches in glusterfs repository Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: nig...@redhat.com Reporter: srang...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org If this[1] proposal goes through, then we would require a Jenkins job that does what is detailed in the mail. I.e, - On non-master branches, validate if provided gerrit "Change-ID" is part of master or not, - If yes, then post a message on the commit stating the same - If not, then post a warning on the commit - This job need not vote, as there maybe cases where this needs to be overridden, say for changes specific to that branch (like release notes for example) -- 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=KzUUfs6Ed5&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1428047] Require a Jenkins job to validate Change-ID on commits to branches in glusterfs repository
https://bugzilla.redhat.com/show_bug.cgi?id=1428047 Shyamsundar changed: What|Removed |Added CC||srang...@redhat.com Flags||needinfo?(srangana@redhat.c ||om) --- Comment #1 from Shyamsundar --- Marking this as NEEDINFO against myself, so that I can unblock it once feedback from the community is recieved over the devel list. Also [1] in description is missing and is now posted here, [1] http://lists.gluster.org/pipermail/gluster-devel/2017-March/052216.html -- 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=a3LzUx1CzK&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
