#444 Fedora Atomic CI pipeline package whitelist
Opened 5 years ago by mvadkert. Modified 5 years ago

The Fedora Atomic CI pipeline currently runs tests only for packages on this list [1]. The "rpm -qa" from a fresh install shows more packages in interest [2].

Is that fine? Shouldn't the pipeline run package level tests for packages in list [2]? The diff of these two can be found here [3].

[1] https://pagure.io/fedora-atomic/raw/f26/f/fedora-atomic-host-base.json
[2] https://github.com/Andrei-Stepanov/wikistat/blob/master/repos-fedora-atomic
[3] https://paste.fedoraproject.org/paste/jVxhRQPPtsBbOovvU4CViA


Note that [1] is pointing to the f26 branch so that part of the reason you are seeing extra packages on the left side of the diff [3] than you should (i.e. kubernetes, etcd, etc).

There are two ways to deal with this.

  • we update the package manifest to be depsolved, (which requires it to be automatically updated by some bot)
  • we create a service that will return the list of packages for a particular ref (which shouldn't be too hard to do in an openshift world) and query that when we need the list of packages.

I'm not sure which would be the best approach.

Yeah, the depsolved data exists in the final tree. Having a service seems fine, though one can just use the ostree CLI nowadays to fetch the commit metadata and use rpm-ostree db list too.

@dustymabe ugh, so wrong diff a bit, thanks for pointing that out. So I guess after you decide @jbieren can pick that new way up in the pipeline, cool :)

Login to comment on this ticket.

Metadata