[opensuse-buildservice] SLE sources do not appear to generate events on message bus
No opensuse.obs.package.update messages appear for updates to SUSE:SLE-15- SP2:GA. Presumably this is not so much an OBS issue as much as the way the sync is going outside the normal usage bounds, hence the email instead of issue. Improving the syncing mechanism to generate events would be much appreciated. Tracking issue from our end: https://github.com/openSUSE/openSUSE-release-tools/issues/2239 -- Jimmy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 9/25/19 7:10 PM, James Berry wrote:
No opensuse.obs.package.update messages appear for updates to SUSE:SLE-15- SP2:GA. Presumably this is not so much an OBS issue as much as the way the sync is going outside the normal usage bounds, hence the email instead of issue.
Improving the syncing mechanism to generate events would be much appreciated. Tracking issue from our end: https://github.com/openSUSE/openSUSE-release-tools/issues/2239
Hi, The problem is a little unexpected to you, but package.update is sent way more often than it should be - and that's why you haven't noticed this before with other sources (as SLE updates don't go through the API but directly to the backend). But see https://openbuildservice.org/help/manuals/obs-admin-guide/obs.cha.administra... package.update is for metadata changes - what you care for here are source changes and those are signaled by package.commit. So changing from package.update to package.commit should solve your problem. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thursday, September 26, 2019 8:07:56 AM CDT Stephan Kulow wrote:
The problem is a little unexpected to you, but package.update is sent way more often than it should be - and that's why you haven't noticed this before with other sources (as SLE updates don't go through the API but directly to the backend).
Sent more often sure, but also sent everytime sources are changed which is why it has not been noticed. The fact that the .update events are not generated for SLE source updates is a bug.
So changing from package.update to package.commit should solve your problem.
If we can workaround the bug and also get a more specific event great, but it was not expected because it differs from all other packages on OBS because of a hidden implementation detail and thus represents a bug. I will leave a listener on with the .commit event and see that SLE changes generate the events. Thanks, -- Jimmy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 26. September 2019, 15:39:10 CEST James Berry wrote:
On Thursday, September 26, 2019 8:07:56 AM CDT Stephan Kulow wrote:
The problem is a little unexpected to you, but package.update is sent way more often than it should be - and that's why you haven't noticed this before with other sources (as SLE updates don't go through the API but directly to the backend).
Sent more often sure, but also sent everytime sources are changed which is why it has not been noticed. The fact that the .update events are not generated for SLE source updates is a bug.
no, it is a bug that .update meta events are created on source changes in all other projects.
So changing from package.update to package.commit should solve your problem. If we can workaround the bug and also get a more specific event great, but it was not expected because it differs from all other packages on OBS because of a hidden implementation detail and thus represents a bug.
I will leave a listener on with the .commit event and see that SLE changes generate the events.
you have a bug and we have a bug. Lets fix both :) But when we fix our bug, you won't get .update calls at all anymore on source changes, so better be faster then us :) -- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Adrian Schröter -
James Berry -
Stephan Kulow