Skip to content

Copr build jobs with different identifiers don't seem to honor configured targets #2131

@nforro

Description

@nforro

Consider the following config:

  - job: copr_build
    trigger: pull_request
    identifier: fedora-and-epel
    targets:
      - fedora-all
      - epel-9
  - job: copr_build
    trigger: pull_request
    specfile_path: epel8/python-specfile.spec
    identifier: epel8
    actions:
      create-archive:
        - python3 setup.py sdist --dist-dir ./epel8/
        - bash -c "ls -1t ./epel8/*.tar.gz | head -n 1"
      get-current-version: python3 setup.py --version
      pre-sync:
        - python3 plans/git_reference.py
    targets:
      - epel-8

  - job: tests
    trigger: pull_request
    identifier: fedora-and-epel
    targets:
      - fedora-all
      - epel-9

  - job: tests
    trigger: pull_request
    identifier: epel8
    targets:
      - epel-8

I would expect only two copr_build jobs with epel8 suffix and no job with epel-8-x86_64 chroot and fedora-and-epel suffix, but this is the job list (test jobs seem to work fine):

jobs

Here is a draft PR to demonstrate the issue: packit/specfile#258

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/configRelated to the configurationarea/coprRelated to the Copr integrationcomplexity/single-taskRegular task; should be done within daysgain/lowDoesn't bring much value to usersimpact/lowAffects only few of the userskind/bugAn unexpected problem or behavior

    Type

    No type

    Projects

    Status

    backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions