There is no reason why a connection to an AMQP broker cannot be opened and
carried into a chroot that has networking disabled: rpm installs already
perform chroot's carrying multiple open Berkeley DB fdnos into the chroot.
___
devel mailing list --
On Sat, Aug 11, 2018 at 10:33 AM Miroslav Suchý wrote:
> As part of migration of fedmsg from ZMQ to AMQP, I would like to revisit
> what is Copr sending to fedmsg.
>
> Right now we are sending:
>
> 'build.start': {
> 'what': "build start: user:{user} copr:{copr}" \
>
On Mon, Aug 13, 2018 at 12:52 AM Jeff Johnson wrote:
> Changing Fedora infrastructure to use AMQP brings up a different usage
> case.
>
> Build systems tend to eventually invoke rpmbuild to do the actual build.
>
> Would you like rpmbuild to, say, send time stamped progress messages
> directly
Changing Fedora infrastructure to use AMQP brings up a different usage case.
Build systems tend to eventually invoke rpmbuild to do the actual build.
Would you like rpmbuild to, say, send time stamped progress messages directly
through AMQP?
The usage case for AMQP messages in rpmbuild starts
