<ykarel> tkajinam, marios|ruck if it's in upgrade job it might be related to versioning thing and iirc it happens after every release until new tags are pushed for master
<ykarel> may be you to recall something with Sem-Ver: api-break
<ykarel> how it was handled in past
<marios|ruck> ykarel: vaguely :)
<marios|ruck> ykarel: but it seems to be fixed now i mean it may be something else
<ykarel> marios|ruck, i think it will be random as dlrn will build package with timestamp so it will depend on when zed/master package last built
<ykarel> https://trunk.rdoproject.org/api-centos9-zed/api/report.html?package=tripleo-ansible vs https://trunk.rdoproject.org/api-centos9-master-uc/api/report.html?package=tripleo-ansible
<marios|ruck> ykarel: ack ok will revisit this in a bit thanks
<ykarel> ack
Dumping the related conversation in #tripleo
<ykarel> tkajinam, marios|ruck if it's in upgrade job it might be related to versioning thing and iirc it happens after every release until new tags are pushed for master /trunk. rdoproject. org/api- centos9- zed/api/ report. html?package= tripleo- ansible vs https:/ /trunk. rdoproject. org/api- centos9- master- uc/api/ report. html?package= tripleo- ansible
<ykarel> may be you to recall something with Sem-Ver: api-break
<ykarel> how it was handled in past
<marios|ruck> ykarel: vaguely :)
<marios|ruck> ykarel: but it seems to be fixed now i mean it may be something else
<ykarel> marios|ruck, i think it will be random as dlrn will build package with timestamp so it will depend on when zed/master package last built
<ykarel> https:/
<marios|ruck> ykarel: ack ok will revisit this in a bit thanks
<ykarel> ack