PACKIT_COMMIT_SHA content differs from the built NVR

[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!)

[lachmanfrantisek]

The task is to:

• provide env.vars to cover both merged hash and head of the PR
• make sure we provide also the correct NVR as an env.var
• clearly document at https://packit.dev/docs/configuration/actions