The new downstream ingestion mechanism won't work without proper spec for modules.

uh oh, is somebody working on this? seems this is a blocker for adoption at least in my team. If not I guess we will have to do it.

We have OSCI-2280 created internally, but it's not WIP yet.

@draval @timitra if get in the changes this week, how long will it take for Hydra to get this in? It is blocking our move to the 1.x message format :(

@draval @timitra if get in the changes this week, how long will it take for Hydra to get this in? It is blocking our move to the 1.x message format :(

if u are using version 1.1.8 ,then it should work, hydra changes are on qa now.but using 1.1.8 if are pushing a message to hydra stage it shouldn't fail

@timitra there is no mapping for modules in https://pagure.io/fedora-ci/messages/blob/master/f/mappings/results though (because modules don't have clearly defined schema for messages yet). Isn't this a problem for hydra?

https://pagure.io/fedora-ci/messages/blob/master/f/schemas schemas are
defined here

On Mon, Sep 6, 2021 at 4:48 PM Michal Srb pagure@pagure.io wrote:

msrb added a new comment to an issue you are following:
@timitra there is no mapping for modules in https://pagure.io/fedora-ci/messages/blob/master/f/mappings/results though (because modules don't have clearly defined schema for messages yet). Isn't this a problem for hydra?

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-ci/messages/issue/110

--
Tiyasha Mitra

Senior Software Engineer

timitra@redhat.com rcoe@redhat.com
M: 7981080387
https://www.redhat.com/

https://pagure.io/fedora-ci/messages/blob/master/f/schemas schemas are
defined here

Yep, and there is no schema for redhat-module artifacts in 1.1.8.

@msrb we are working on it

@timitra seems there is some confusion, what we are saying is that we will need 1.1.9 and changes related to this issue (we are working on them).

how long will it take to get 1.1.9 to staging and how long to production?

Our CI releases are blocked on this ...

i have already made changes regarding empty array in pagure rep 1.1.8
,hydra changes are on qa,once it is verified, it will move to stage

On Mon, Sep 6, 2021 at 5:18 PM Miroslav Vadkerti pagure@pagure.io wrote:

mvadkert added a new comment to an issue you are following:
``
@timitra seems there is some confusion, what we are saying we will need
1.1.9 and changes related to this issue (we are working on them).

how long will it take to get the to staging and how long to production?

Our CI releases are blocked on this ...
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-ci/messages/issue/110

--
Tiyasha Mitra

Senior Software Engineer

timitra@redhat.com rcoe@redhat.com
M: 7981080387
https://www.redhat.com/

@timitra this issue is not about empty arrays, it is about another type of artifact redhat-module

@timitra this issue is not about empty arrays, it is about another type of artifact redhat-module
we will be able to tell that once this module is available and we are sending hydra messages

@timitra this issue is not about empty arrays, it is about another type of artifact redhat-module
we will be able to tell that once this module is available and we are sending hydra messages

ok :)

The PR that adds support for modules has been merged. Thanks everyone who helped to make this happen. Especially to @efedin for the code, and @mvadkert for jumping on this so quickly and leading the effort. You guys rock :rocket: :clap:

I cannot close this issue for some reason, so someone else will need to do that :)