packit: Update config and sync to Fedora

[LorbusChris]

With this change:

• COPR builds are now run per-PR
• Packit will open PRs to the Fedora dist-git repo when a new release is created
• the %global commit0 value is updated in the specfile for each build

cc @haircommander

What type of PR is this?

/kind ci

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

packit: Update config and sync to Fedora

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 1: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 2: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 3: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 4: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 5: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 6: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 7: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 8: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 9: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 1: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 2: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 3: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 4: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 5: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 6: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 7: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 8: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 9: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 1: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 2: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 3: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 4: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 5: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 6: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 7: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 8: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 9: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[openshift-ci]

Hi @LorbusChris. Thanks for your PR.

I'm waiting for a cri-o member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #7922 (7084db2) into main (93b05e5) will not change coverage.
Report is 4 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7922   +/-   ##
=======================================
  Coverage   48.87%   48.87%           
=======================================
  Files         152      152           
  Lines       16447    16447           
=======================================
  Hits         8038     8038           
  Misses       7433     7433           
  Partials      976      976           

[kannon92]

/ok-to-test

[kannon92]

Please add a release note to the block in the description.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 1: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 2: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 3: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 4: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 5: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 6: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 7: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 8: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 9: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 1: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 2: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 3: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 4: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 5: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 6: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 7: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 8: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 9: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 1: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 2: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 3: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 4: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 5: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 6: {'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 7: {'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 8: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}, 9: {'fedora-rawhide': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-40': ["'specfile_path' is not specified or no specfile was found in the repo"], 'fedora-39': ["'specfile_path' is not specified or no specfile was found in the repo"]}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[LorbusChris]

/packit copr_build

[LorbusChris]

This should be good to go now. Please take a look if you get a chance @haircommander.

[haircommander]

/lgtm
/approve

/retest

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, LorbusChris

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [haircommander]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[LorbusChris]

/retest-required

[LorbusChris]

/retest-required

[haircommander]

/override ci/prow/ci-fedora-integration

[openshift-ci]

@haircommander: Overrode contexts on behalf of haircommander: ci/prow/ci-fedora-integration

In response to this:

/override ci/prow/ci-fedora-integration

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[haircommander]

/override ci/prow/ci-cgroupv2-integration

[openshift-ci]

@haircommander: Overrode contexts on behalf of haircommander: ci/prow/ci-cgroupv2-integration

In response to this:

/override ci/prow/ci-cgroupv2-integration

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[haircommander]

/override ci/prow/e2e-gcp-ovn

[openshift-ci]

@haircommander: Overrode contexts on behalf of haircommander: ci/prow/e2e-gcp-ovn

In response to this:

/override ci/prow/e2e-gcp-ovn

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[LorbusChris]

/test ci-e2e-evented-pleg