Skip to main content

17 posts tagged with "2024"

View All Tags

· One min read
Laura Barcziová

Week 7 (February 13th – February 19th)​

  • Packit now supports special value ignore for trigger in jobs configuration that indicates not to execute the job at all. This can be useful for templates or temporarily disabled jobs. (packit#2234)
  • We have fixed the caching of data for the usage API endpoint. (packit-service#2350)
  • We have fixed an issue that caused loading the same data multiple times on the dashboard within the project views. (packit-service#2349)
  • We have also fixed crashing of dashboard's Usage page in case of unsuccessful queries. (dashboard#378)
  • We have fixed parsing of resolved Bugzillas in comments with multiple arguments specified, e.g. /packit pull-from-upstream --with-pr-config --resolved-bugs rhbz#123. (packit-service#2346)

· One min read
Maja Massarini

Week 6 (February 6th – February 12th)​

  • Packit now searches for bugzilla about new release created by Upstream Release Monitoring to reference each time it syncs the release downstream. (packit#2229)
  • We have introduced new CLI command packit dist-git init that initializes Packit configuration for release automation in dist-git repository. (packit#2225)
  • We have introduced new configuration options require.label.present and require.label.absent. By configuring these you can specify labels that need to be present or absent on a pull request for Packit to react on such PR. (packit-service#2333)
  • Interface for labels was unified and labels property for PullRequest and Issue now return list of PRLabel and IssueLabel respectively. (ogr#839)

· One min read
Maja Massarini

Week 5 (January 30th – February 5th)​

  • packit validate-config now checks whether the Upstream Release Monitoring for the package is correctly configured if pull_from_upstream job is present in the configuration. (packit#2226)
  • There is a new global configuration option parse_time_macros that allows to configure macros to be explicitly defined or undefined at spec file parse time. (packit#2222)
  • We have added additional retries and improvements for task processing. (packit-service#2326)

· One min read
Matej Focko

Week 4 (January 23rd – January 29th)​

  • pull-from-upstream and propose-downstream commands now have the --sync-acls option that enables syncing the ACLs between dits-git repo and fork. The default behaviour was, however, changed to not sync the ACLs. (packit#2214)
  • Packit now properly handles exceptions when syncing ACLs during release syncing. (packit#2213)
  • allowed_pr_authors and allowed_committers now allow specifying groups and also aliases all_admins and all_committers (corresponding to the access to the repository). (packit-service#2320)
  • ogr now supports 2 new methods for Pagure: one for getting users with specified access rights and one for getting members of a group. (ogr#834)

· One min read
František Lachman

Week 3 (January 16th – January 22nd)​

  • Packit now properly handles exceptions when syncing ACLs during release syncing. (packit#2213)
  • We have fixed a bug in handling chroot-specific configuration once the chroots themselves are updated. (packit#2194)
  • We have increased the number of retries of Fedora release syncing for situations where the tarball is uploaded some time after the release happens. (packit-service#2307)
  • There is a new API endpoint /bodhi-updates for getting information about Bodhi updates submitted by Packit. (packit-service#2310)
  • For /packit test command, you can now also use -i and --id aliases for --identifier option. (packit-service#2309)

· One min read
Nikola Forró

Week 1 (January 2nd – January 8th)​

  • We have changed the behaviour of loading Packit configuration for koji_build and bodhi_update jobs. For both of them, the behaviour is the same as for pull_from_upstream - the configuration is taken from the default branch of the dist-git repository (usually rawhide) and other branches are ignored. (packit-service#2295)