Skip to content

PACKIT_COMMIT_SHA content differs from the built NVR #2329

Open
@praiskup

Description

@praiskup

What happened? What is the problem?

The merge_pr_in_ci config is true by default, so the Copr build contains a merge (target) sha in RPMs' NVRs. This sha is not visible anywhere.

The $PACKIT_COMMIT_SHA though contains the bare SHA from git push.

This situation can cause big headaches when the TF test cases attempt to find the corresponding NVRs using PACKIT_COMMIT_SHA.

Workaround is to set merge_pr_in_ci: false.

What did you expect to happen?

The $PACKIT_COMMIT_SHA should contain the same have the built RPMs. No matter the merge_pr_in_ci config.

Example URL(s)

No response

Steps to reproduce

Let the Copr build finish, and compare the RPMs' NVS with `git show` SHA, the hashes are different.

What is the impacted category (job)?

Testing Farm tests

Workaround

  • There is an existing workaround that can be used until this issue is fixed.

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/testing-farmRelated to Testing Farm integration.complexity/single-taskRegular task, should be done within days.gain/highThis brings a lot of value to (not strictly a lot of) users.impact/lowThis issue impacts only a few users.kind/bugSomething isn't working.

    Type

    No type

    Projects

    • Status

      backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions