Hacker News Reader

> quite a few build systems are now turning to MQ's for build systems

References? I'm curious as to who's doing this and why. I'm trying to think of a reason and not coming up with much.

We have started using a MQ to send messages between different Jenkins instances. For example to have long running test executions on a dedicated jenkins-instance so the main build-jenkins can be restarted without affecting the tests.

Curious how you've set this up. What role does the MQ play? Does it ship results to the mother ship or a console? Or are you sending notices of changes to the test machine? etc. TIA

We have custom plugin to send message to the MQ. Other Jenkins-instances running the same plugin will receive the message and can act on them according to the configuration.

Currently we mostly use this to send internal release notifications around, e.g. "foobar-1.0.0 released, find it here <path to RPM>". Kind of neat with a n * 1000 developer organization spread over the entire world.

Currently the plugin is not open source but hopefully it will be later on.

Very cool. Thanks for the explanation!

pybit, my organisations very own rbit.

THink replacing Jenkins not make

Reply on news.ycombinator.com