Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reuse build targets from Packit as a Service in CLI

See original GitHub issue

At this moment my .packit.yaml file looks like this.

# See the documentation for more information:
# https://packit.dev/docs/configuration/

specfile_path: specfiles/restraint-upstream.spec

# add or remove files that should be synced
synced_files:
  - src: restraint-upstream.spec
    dest: restraint.spec

upstream_package_name: restraint
# downstream (Fedora) RPM package name
downstream_package_name: restraint

jobs:
- job: copr_build
  trigger: pull_request
  metadata:
    targets:
      - centos-stream-aarch64
      - centos-stream-ppc64le
      - centos-stream-x86_64
      - fedora-30-aarch64
      - fedora-30-armhfp
      - fedora-30-i386
      - fedora-30-ppc64le
      - fedora-30-s390x
      - fedora-30-x86_64
      - fedora-31-aarch64
      - fedora-31-armhfp
      - fedora-31-i386
      - fedora-31-ppc64le
      - fedora-31-s390x
      - fedora-31-x86_64
      - fedora-rawhide-aarch64
      - fedora-rawhide-armhfp
      - fedora-rawhide-i386
      - fedora-rawhide-ppc64le
      - fedora-rawhide-s390x
      - fedora-rawhide-x86_64
      - rhel-8-aarch64
      - rhel-8-ppc64
      - rhel-8-ppc64le
      - rhel-8-x86_64

As you can see we are running huge number of build targets. I would like to run build before I create the PR in GH. This means I have to put there manually 25 targets. It would be nice if we can unify this so my packit copr-build will use the same targets as PR.

Issue Analytics

State:
Created 4 years ago
Comments:12 (11 by maintainers)

Top GitHub Comments

1reaction

lachmanfrantisekcommented, Feb 12, 2020

But, what will happen if Fedora will scrape one arch in Fedora Rawhide? For example, killing 32 bits arch @lachmanfrantisek

Then you can use fedora-stable and fedora-development:

fedora-development-arch1
fedora-development-arch2
fedora-stable-arch1
fedora-stable-arch2
fedora-stable-arch3

1reaction

lachmanfrantisekcommented, Feb 12, 2020

Side note: some lines can be saved with aliases:

jobs:
- job: copr_build
  trigger: pull_request
  metadata:
    targets:
      - centos-stream-aarch64
      - centos-stream-ppc64le
      - centos-stream-x86_64
      - fedora-all-aarch64
      - fedora-all-armhfp
      - fedora-all-i386
      - fedora-all-ppc64le
      - fedora-all-s390x
      - fedora-all-x86_64
      - rhel-8-aarch64
      - rhel-8-ppc64
      - rhel-8-ppc64le
      - rhel-8-x86_64

You then no need to change that so often…