Skip to main content

4 posts tagged with "September"

View All Tags

· One min read

Week 39 (September 26th – October 2nd)

  • When using packit CLI you can now specify bugs resolved by an update by -b or --resolve-bug option for propose-downstream and pull-from-upstream commands. The values will be added by default to the changelog and commit message and provided in commit-message and changelog-entry actions as PACKIT_RESOLVED_BUGS env variable. (packit#2094)
  • Packit-service now automatically adds bugzilla created by Upstream Release Monitoring as - Resolves {bugzilla} to the changelog (or commit if autochangelog is used) and provides the value in commit-message and changelog-entry actions as PACKIT_RESOLVED_BUGS env variable. When retriggering the pull-from-upstream from comment, one can also specify the bug(s) as /packit pull-from-upstream --resolved-bugs rhbz#123,rhbz#125 and Packit will do the same. (packit-service#2193)
  • You can now configure notifications.failure_comment.message also for downstream jobs, where the configured message will be used as an extension of the comment added by default by Packit. (packit-service#2199)

· One min read

Week 38 (September 19th – September 25th)

  • As part of the effort of implementing release syncing for CentOS Stream, Packit now supports the pkg_tool option in the config (at the top-level or with specific packages when using the monorepo syntax). This option can be used for switching between fedpkg or centpkg. (packit#2085)
  • When updating the Version tag during propose_downstream or pull_from_upstream, Packit now tries to update referenced macros (if any) rather than overwriting the references. (packit#2087)

· One min read

Week 37 (September 12th – September 18th)

  • If you have concerns about Packit uploading new archives to lookaside cache before creating a pull request, you can newly set upload_sources to False to disable this. (packit#2086)
  • We have introduced a new configuration option notifications.failure_comment.message that enables notifying users on failure via a comment using the configured message. (packit-service#2182)

· One min read

Week 36 (September 5th – September 11th)

  • Packit now supports commit-message action that can be used to override the default commit message produced by Packit during propose-downstream or pull-from-upstream. Please pay attention to our documentation with regards to the usage of this action. (packit#2070)
  • Packit CLI now supports testing the pull-from-upstream workflow. Use the packit pull-from-upstream command from the packit RPM package. (packit#2063)
  • Packit now passes initiator context for tmt to the Testing Farm. You can use this option to run or skip certain tests when they're run by Packit. (packit-service#2176)
  • Testing Farm started additionally exposing regexes on top of the exact compose names in the /composes/ endpoints, and we now support this as well when checking the validity of compose. (packit-service#2168)
  • We have disabled the jitter for retrying Bodhi update tasks to prevent race conditions causing not created updates. (packit-service#2170)
  • We have fixed a bug in get_fork method for Pagure about checking the usernames for a match when going through existing forks. (ogr#800)