On 05/26/2016 03:07 PM, Jeremy Stanley wrote:
> On 2016-05-26 14:23:38 -0400 (-0400), Sean Dague wrote:
> [...]
>> It does run on a custom port... so the great firewall of China is still
>> probably an issue.
> [...]
>
> I had assumed websockets could be a solution there?
> http://jpmens.net/2014/
On 26/05/16 14:06, Jeremy Stanley wrote:
On 2016-05-26 11:37:18 +0100 (+0100), Zara Zaimeche wrote:
[...]
Updating the bug/task-tracker from those changes, however, would
be different for each tracker, so you wouldn't be able to do that
part in a generic way. Plus, while analyzing the data fro
On 2016-05-26 14:23:38 -0400 (-0400), Sean Dague wrote:
[...]
> It does run on a custom port... so the great firewall of China is still
> probably an issue.
[...]
I had assumed websockets could be a solution there?
http://jpmens.net/2014/07/03/the-mosquitto-mqtt-broker-gets-websockets-support/
>
On 05/26/2016 02:11 PM, Matthew Treinish wrote:
> On Thu, May 26, 2016 at 05:55:34PM +, Jeremy Stanley wrote:
>> On 2016-05-26 12:54:49 -0400 (-0400), Matthew Treinish wrote:
>>> Just a quick follow-up I started running this on a throwaway server at
>>> 15.184.138.236. So you can subscribe to e
On Thu, May 26, 2016 at 05:55:34PM +, Jeremy Stanley wrote:
> On 2016-05-26 12:54:49 -0400 (-0400), Matthew Treinish wrote:
> > Just a quick follow-up I started running this on a throwaway server at
> > 15.184.138.236. So you can subscribe to events from gerrit.
> [...]
>
> How resource-intens
On 2016-05-26 12:54:49 -0400 (-0400), Matthew Treinish wrote:
> Just a quick follow-up I started running this on a throwaway server at
> 15.184.138.236. So you can subscribe to events from gerrit.
[...]
How resource-intensive is it? Curious whether it makes sense to run
something like this directl
On 2016-05-26 09:57:58 -0700 (-0700), Zaro wrote:
> 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.
[...]
That's a ver
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
On Wed, May 25, 2016 at 10:08:57PM -0400, Matthew Treinish wrote:
> On Wed, May 25, 2016 at 02:43:36PM -0400, Sean Dague wrote:
> > On 05/25/2016 01:54 PM, Spencer Krum wrote:
> > >
> > > When working on a previous project, Nikki wrote this tool as a general
> > > purpose hook into gerrit:
> > >
On 2016-05-26 11:37:18 +0100 (+0100), Zara Zaimeche wrote:
[...]
> Updating the bug/task-tracker from those changes, however, would
> be different for each tracker, so you wouldn't be able to do that
> part in a generic way. Plus, while analyzing the data from the
> stream could theoretically be th
On 25/05/16 18:44, Anita Kuno wrote:
On 05/25/2016 01:13 PM, Jeremy Stanley wrote:
On 2016-05-25 11:43:39 -0500 (-0500), Gregory Haynes wrote:
[...]
We are considering making a small project to connect to and read
from the Gerrit event stream and then update our bug tracker.
[...]
If we imp
On Wed, May 25, 2016 at 02:43:36PM -0400, Sean Dague wrote:
> On 05/25/2016 01:54 PM, Spencer Krum wrote:
> >
> > When working on a previous project, Nikki wrote this tool as a general
> > purpose hook into gerrit:
> >
> > https://github.com/notnownikki/zoidberg
> >
> > I don't think she is acti
On 05/26/2016 04:43 AM, Sean Dague wrote:
One thing I've been thinking a bit about is whether the event stream
could get into something like MQTT easily.
Although larger in scope than just gerrit, Fedora has something very
similar to this with fedmsg [1]
It is a pretty cool idea to have everyt
On 05/25/2016 01:54 PM, Spencer Krum wrote:
>
> When working on a previous project, Nikki wrote this tool as a general
> purpose hook into gerrit:
>
> https://github.com/notnownikki/zoidberg
>
> I don't think she is actively maintaining or using it right now though.
One thing I've been thinking
When working on a previous project, Nikki wrote this tool as a general
purpose hook into gerrit:
https://github.com/notnownikki/zoidberg
I don't think she is actively maintaining or using it right now though.
--
Spencer Krum
n...@spencerkrum.com
__
On 05/25/2016 01:13 PM, Jeremy Stanley wrote:
> On 2016-05-25 11:43:39 -0500 (-0500), Gregory Haynes wrote:
> [...]
>> We are considering making a small project to connect to and read
>> from the Gerrit event stream and then update our bug tracker.
> [...]
>> If we implemented this, would this be s
On 2016-05-25 11:43:39 -0500 (-0500), Gregory Haynes wrote:
[...]
> We are considering making a small project to connect to and read
> from the Gerrit event stream and then update our bug tracker.
[...]
> If we implemented this, would this be something the -infra project
> would like to have live u
On Wed, May 25, 2016, at 11:55 AM, Jimmy Mcarthur wrote:
> I'm not sure about Infra, but we're in the same boat with one of our bug
> trackers. This would be awesome to have and I'm sure we would use it.
>
> Out of curiosity, what bug tracker are you currently using?
GitHub Enterprise, although
I'm not sure about Infra, but we're in the same boat with one of our bug
trackers. This would be awesome to have and I'm sure we would use it.
Out of curiosity, what bug tracker are you currently using?
Cheers,
Jimmy
Gregory Haynes wrote:
Hello -Infra folks,
While setting up an OpenStack-inf
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
20 matches
Mail list logo
