#230 critpath location changed
Opened by kparal. Modified

The existing URL we used to retrieve critpath (from pkgdb) is supposed to be obsolete now:
https://admin.fedoraproject.org/pkgdb/api/critpath?format=json
It's not going to be updated anymore. Critpath lives in PDC now. Here's an example how to retrieve that:
https://pagure.io/releng/pull-request/6858#_1,97

Replace our current solution for retrieving critpath in ansible with the new approach.


Metadata Update from @kparal:
- Issue priority set to: High
- Issue tagged with: infra

On stg this stopped working completely:
https://admin.stg.fedoraproject.org/pkgdb/api/critpath?format=json

Because of that, no koji build tasks run on taskotron-stg. So this is getting even more important.

@jsedlak you had some PoC code, can you share it?

On stg this stopped working completely:
https://admin.stg.fedoraproject.org/pkgdb/api/critpath?format=json

This has been fixed for the moment by puiterwijk.

I didn't know where to put it so I put it into taskotron trigger here until you'll decide where this code should be. pdc-client needs to be updated: https://bugzilla.redhat.com/show_bug.cgi?id=1484780, in the meantime you can set "develop=True" in /etc/pdc/fedora.json.

Note: Some links are also mentioned at https://fedoraproject.org/wiki/Critical_path_package

Since we no longer need critpath for abicheck (see taskotron#238) this can get a lower priority.

Metadata Update from @kparal:
- Issue priority set to: Low (was: High)

See https://github.com/product-definition-center/product-definition-center/blob/master/docs/source/using_api.rst#paging to learn how to configure paging in PDC (to make the queries a bit more efficient).

In https://pagure.io/taskotron/taskotron-trigger/pull-request/53 I've made critpath file optional. PDC is going away, and the new location hasn't been announced yet. Fortunately, we don't need critpath at the moment for any task.

Metadata