Bug 1665889 - Too small restriction for commit topic length in review.gluster.org
Summary: Too small restriction for commit topic length in review.gluster.org
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-14 11:07 UTC by Valerii Ponomarov
Modified: 2019-01-14 11:42 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-14 11:42:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Valerii Ponomarov 2019-01-14 11:07:27 UTC
Description of the problem:
We, OCS QE automation team, have goal to port our downstream project [1] to the upstream [2]. And we are unable to do it, because new repo [2] has limitation to the length of a commit topic as 50 symbols. In our downstream project we followed 72 symbols length. So, need to make it be 72 symbols.

[1] http://git.app.eng.bos.redhat.com/git/cns-qe/cns-automation.git/
[2] https://github.com/gluster/glusterfs-containers-tests

Version-Release number of selected component (if applicable):

How reproducible: 100%

Steps to Reproduce:
1. Create commit
2. Push it to the gerrit -> https://review.gluster.org/#/q/project:glusterfs-containers-tests

Actual results:
Response from server:
remote: (W) efd7f6f: commit subject >50 characters; use shorter first paragraph

Expected results:
Success after attempt to push code.

Additional info:

Comment 1 Nigel Babu 2019-01-14 11:23:08 UTC
Ack. This needs a gerrit config change and a restart. I'm going to do that now.

Comment 2 Nigel Babu 2019-01-14 11:42:59 UTC
This still lead to some permission troubles around pushing merge commits that did not go away despite granting merge permissions. I did the push instead and that has worked.


Note You need to log in before you can comment on or make changes to this bug.