+1 since it will save me some time, at least. I usually post a comment on a JIRA ticket once it's resolved, adding information about git commit hash of the change that contains the fix. With this integration in place, there will be no need to do that.
/Alexey On Fri, Nov 8, 2019 at 8:07 PM Attila Bukor <[email protected]> wrote: > I’m +1 on this as well. It would be nice to be able to find the commit > right from the JIRA. > > Sent from my iPhone > > > On Nov 8, 2019, at 7:57 PM, Grant Henke <[email protected]> > wrote: > > > > +1 This would be great > > > >> On Fri, Nov 8, 2019 at 12:53 PM Andrew Wong <[email protected]> wrote: > >> > >> SGTM. My first thought was that the issues mailing list might get more > >> traffic, but I'm ok with that, since contributors today often try to > post > >> an equivalent comment anyways. This just makes that more consistent. > >> > >> On Fri, Nov 8, 2019, 10:45 AM Todd Lipcon <[email protected]> > >> wrote: > >> > >>> Sounds nice to me > >>> > >>> On Fri, Nov 8, 2019 at 10:44 AM Adar Lieber-Dembo > >>> <[email protected]> > >>> wrote: > >>> > >>>> Hi devs, > >>>> > >>>> The Apache Impala project has this neat integration set up between > >> gitbox > >>>> and JIRA where if someone pushes a new commit to gitbox and that > commit > >>> has > >>>> a JIRA associated with it, the push generates a JIRA comment > describing > >>> the > >>>> commit that was just pushed. You can see an example of this here: > >>>> https://issues.apache.org/jira/browse/IMPALA-6478 > >>>> > >>>> I think this is pretty useful and I’d get it enabled for Kudu too. > Does > >>>> anyone object? If I don’t hear any objections by next Wednesday I’ll > go > >>>> ahead and file an INFRA ticket. > >>>> > >>> > >>> > >>> -- > >>> Todd Lipcon > >>> Software Engineer, Cloudera > >>> > >> > > > > > > -- > > Grant Henke > > Software Engineer | Cloudera > > [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke > >
