[Gluster-infra] [Bug 1171650] Gerrit: configure clickable links to bugzilla

2016-05-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1171650

Kaushal  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |WORKSFORME
Last Closed||2016-05-12 00:21:00



--- Comment #8 from Kaushal  ---
The linking has been enabled for sometime and is working well. Closing this
now.

-- 
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=EGpCgPrMX4&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1171650] Gerrit: configure clickable links to bugzilla

2015-04-26 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1171650



--- Comment #7 from Kaushal  ---
Added linking for CIDs and Change-Ids.

-- 
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=tCsWnWlEmZ&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1171650] Gerrit: configure clickable links to bugzilla

2015-04-26 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1171650



--- Comment #6 from Kaushal  ---
(In reply to Kaushal from comment #5)
> 
> It keeps redirecting me to my coverity user dashboard.
> 

I had to visit the defects view once, to get the link to work without being
redirected to my dashboard. I'll add this as well.

-- 
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=a7We0lSHOB&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1171650] Gerrit: configure clickable links to bugzilla

2015-04-26 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1171650



--- Comment #5 from Kaushal  ---
(In reply to Niels de Vos from comment #4)
> This seems to work:
> 
>
> https://scan6.coverity.com:8443/query/defects.htm?projectId=10714&cid=1288824
> 

It keeps redirecting me to my coverity user dashboard.

> 
> Backports often should have the same Change-Id. This makes it easy to
> identify backports and their original change. A Change-Id needs to be unique
> per branch, different branches (master, release-3.7, ...) can have the same
> Change-Id. Example:
> 
> http://review.gluster.org/#/q/I62168a0ab4f0c78e61987371ae75a0d2dd56ced8

The gerrit documentation recommends having different change-ids for backports.
Each backport is a unique commit, so it should have a unique change-id for
gerrit to be able to track it. This was how I thought gerrit should have
worked, but apparently you can have duplicate change-ids. Whenever I've
backported changes I've always had the change-id regenerated. I believe this is
how most of the developers did backports.

I'll add the commentlink setting anyway.

-- 
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=GLoSpbvCLo&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1171650] Gerrit: configure clickable links to bugzilla

2015-04-26 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1171650

Niels de Vos  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|b...@gluster.org|kaus...@redhat.com



--- Comment #4 from Niels de Vos  ---
(In reply to Kaushal from comment #3)
> r.g.o now has clickable links to bugzilla.

Great, thanks!

> I'll also add links to Coverity, if I can figure out a direct URI to the CID
> page.

This seems to work:

   
https://scan6.coverity.com:8443/query/defects.htm?projectId=10714&cid=1288824


> About, Change-Id's though, they are supposed to be unique to each review. So
> if a patch were to be backported, it would have a different Change-Id to the
> original.

Backports often should have the same Change-Id. This makes it easy to identify
backports and their original change. A Change-Id needs to be unique per branch,
different branches (master, release-3.7, ...) can have the same Change-Id.
Example:

http://review.gluster.org/#/q/I62168a0ab4f0c78e61987371ae75a0d2dd56ced8

-- 
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=1IbN7wTer9&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1171650] Gerrit: configure clickable links to bugzilla

2015-04-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1171650

Kaushal  changed:

   What|Removed |Added

 CC||kaus...@redhat.com



--- Comment #3 from Kaushal  ---
r.g.o now has clickable links to bugzilla.

I'll also add links to Coverity, if I can figure out a direct URI to the CID
page.

About, Change-Id's though, they are supposed to be unique to each review. So if
a patch were to be backported, it would have a different Change-Id to the
original.

-- 
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=f9pLYUrAyf&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra