Parts of jeepyb for gerrit and issue tracking functionality should really be deprecated. Gerrit allows issue tracking integration with its set of its-* based plugins. There's one for bugzilla, jira, and even storyboard. However those probably won't help since it does need to connect directly to the issue tracker. I'm guessing what might help is the rabbitmq plugin. I'm not sure if it would be too heavyweight for your needs but you might want to take a look, https://gerrit.googlesource.com/plugins/rabbitmq/
-Khai On Wed, May 25, 2016 at 9:43 AM, Gregory Haynes <[email protected]> wrote: > Hello -Infra folks, > > While setting up an OpenStack-infra style testing infrastructure we have > run in to the need for a tool to update our issue tracker in a different > manner than the current Gerrit -> jeepyb system used for OpenStack. Our > issue boils down to the fact that our bug tracker lives on a network our > Gerrit cannot initiate a connection in to. As a result we need something > to connect to Gerrit from within our bug tracker's network. We are > considering making a small project to connect to and read from the > Gerrit event stream and then update our bug tracker. > > > My hope with this email was to see if: > > Is there something (aside from not having crazy network requirements) > were missing that might make this project unnecessary? > > If we implemented this, would this be something the -infra project would > like to have live upstream? It seems easy enough to make this generally > useful to others with similar requirements. > > Any other thoughts/comments that might help :). > > Thanks, > Greg > > -- > Gregory Haynes > [email protected] > > _______________________________________________ > OpenStack-Infra mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra _______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
