Skip to main content

11 posts tagged with "April"

View All Tags

· One min read
Alžběta Kučerová

Week 15 (April 7th – April 13th)​

  • In addition to version_update_mask, users can now use a new version_update_specifiers configuration option to control the upstream versions allowed to be release-synced. The option accepts PEP440 version specifier sets, for example version_update_specifiers: >=1.0,~=1.0. (packit#2710)
  • Packit is now able to handle multi-level project namespaces. (packit-service#3092)
  • We have fixed a bug in relation to retriggering of Copr builds sometimes failing due to a failed cancellation of previous builds. (packit-service#3099)
  • We have fixed tag filtering not working when processing multi-release events and when retriggering pull-from-upstream. (packit-service#3098)
  • As part of the process of the integration of Log Detective into Packit, Packit now ignores Log Detective messages in case Log Detective integration is disabled by the user by setting logdetective_enabled to False in the service configuration file. (packit-service#3100)
  • We have fixed a bug that would lead to Testing Farm jobs being cancelled when there were no associated Copr builds. (packit-service#3102)

· One min read
Laura Barcziová

Week 14 (April 1st – April 7th)​

  • Packit now cancels running jobs even after manual retriggering. (packit-service#3076)
  • You can now configure multiple pull-from-upstream jobs with different version/tag filters. In conjunction with the Monitoring all release monitoring option this allows you to consume multiple release streams and freely configure Fedora releases you want to target with each. (packit-service#3083)
  • We have increased the retries for transient errors during Bodhi updates submission. (packit-service#3090)

· One min read
František Lachman

Week 14 (April 1st – April 7th)​

  • When using fast_forward_merge_into, version_update_mask is now correctly being taken into consideration. (packit#2551)
  • We have introduced a new config command group for configuration-related commands and moved the validate-config command under it, resulting in the new command being packit config validate. (packit#2559)
  • It is now possible to retrigger dist-git CI scratch builds with /packit scratch-build. (packit-service#2770)

· One min read
Nikola Forró

Week 18 (April 30th – May 6th)​

  • Packit will now upload to lookaside cache sources that are not specified by URLs and are present in the dist-git repo during release sync. Additionally, all the actions ran during syncing release will provide the PACKIT_PROJECT_VERSION environment variable. (packit#2297)
  • We have introduced a new status_name_template option that allows you to configure status name for a Packit job. For further details have a look at our docs. This feature is still experimental and at the moment it is not possible to retry such jobs via GitHub Checks' re-run. (packit-service#2402)

· One min read
Laura Barcziová

Week 17 (April 23rd – April 29th)​

  • We have fixed the syncing of ACLs during CentOS Stream release syncing. (packit#2298)
  • koji_build job has a new sidetag_group option that allows to perform a downstream Koji build in a sidetag. A new sidetag will be created for each configured dist_git_branch if it doesn't already exist. This represents the first step towards multi-package Bodhi updates. Stay tuned for further advancements! (packit-service#2409)
  • We have fixed an issue when copr_build job status checks were sometimes wrongly updated with a misleading message after a SRPM build failure. (packit-service#2406)

· One min read
Matej Focko

Week 16 (April 16th – April 22nd)​

  • packit dist-git init now allows specifying --version-update-mask option and also any arbitrary top-level configuration options. (packit#2288)
  • We have fixed Packit auto-referencing Upstream Release Monitoring bug for release syncing to CentOS Stream. (packit#2284)
  • We have changed the behaviour of /packit test comment command: in case there is a missing build for some target, the build will not be triggered anymore, it will just be reported to the user. We needed to make this change as with the increased complexity of the configuration (multiple test jobs), the previous implementation was prone to race conditions leading to wasting of resources of Copr and Testing Farm. (packit-service#2399)