Skip to main content

· One min read
Laura Barcziová

Week 4 (January 20th – January 26th)​

  • Testing jobs running against dist-git PRs now have the dist-git-branch context pointing to the target branch of the PR. (packit-service#2935). On epel10.y dist-git PRs they now use the CentOS Stream 10 Testing Farm compose, same as epel10. (packit-service#2953)
  • Packit now supports the --package parameter, which can be used when retriggering jobs in monorepositories via comments. The parameter is intended to specify the package, for which to run specified jobs. (packit-service#2850)

· One min read
Maja Massarini

Week 3 (January 14th – January 20th)​

  • For Fedora CI, we are now providing direct links to Koji/Testing Farm instead of our dashboard, when possible. (packit-service#2943)
  • Packit as Fedora CI now triggers ELN builds and test jobs on rawhide pull requests of onboarded ELN packages that don't have designated eln branch. (packit-service#2950)
  • We have fixed a race condition that was preventing completed Testing Farm tests from being reported by the Packit service on the dashboard and in pull requests. (packit-service#2952)

· One min read
Nikola Forró

Week 1 (January 1st – January 5th)​

  • For retriggering tests with builds from another pull request, Packit now supports Github's automatically converted URL format (https://github.com/namespace/repo/pull/<pr_id>, e.g. /packit test https://github.com/namespace/repo/pull/<pr_id>) (packit-service#2923)

· One min read
Marek Blaha

Week 49 (December 2nd – December 9th)​

  • packit init now automatically retrieves the latest version of the pre-commit hook to be added to the user's pre-commit configuration file. (packit#2651)
  • Fixed a bug that could prevent downstream jobs from being triggered in case dist-git spec file depends on other files and is not parseable on its own. (packit-service#2901)

· One min read
Nikola Forró

Week 48 (November 25th – December 1st)​

  • There were no user-facing changes in packit(-service) this week
  • The team is back in full strength and we plan to gradually address any technical debt
  • The work on Log Detective integration to Packit has started