45 posts tagged with "2024"

Week 37 (September 10th – September 16th)​

• We have fixed showing of Bodhi updates that are triggered by non-Packit Koji builds on our dashboard. (packit-service#2528)

Week 36 (September 3rd – September 9th)​

• Packit now supports passing custom arguments to various static analyzers through --csmock-args CLI option and csmock_args configuration. (packit#2402)
• When syncing a new release, Packit can now avoid diverging git branches by reusing the commit from one branch when opening pull requests into other branches. (These pull requests can be merged in fast-forward mode.) Use the new syntax for dist_git_branches as in this example to utilise this functionality:

{
  "rawhide": {
    "fast_forward_merge_into": ["f40"]
   },
  "fedora-stable": {}
}

(packit-service#2478)

Week 34 (August 20st – August 27th)​

• pull-from-upstream is now supported also without specifying upstream_project_url in the configuration. For such cases, the upstream repository will not be detected and cloned during release syncing. (packit#2398)
• dist-git init command now allows upstream-git-url not to be specified. (packit#2387)
• You can newly tag builds of a package into a sidetag group by using /packit koji-tag comment command. (packit-service#2507)
• Thanks to Cristian Le, epel-10 is now correctly mapped to a centos-stream-10 when running tests. (packit-service#2508)

Week 33 (August 13th – August 19th)​

• Several internal, but also performance improvements were done on our dashboard, thanks to Freya Gustavsson (packit/dashboard#435)!

Week 32 (August 6th – August 12th)​

• Packit now passes PACKIT_TAG_NAME to the Testing Farm run when it's triggered by a release event. Thanks @Frawless. (packit-service#2494)

Week 31 (July 30th – August 5th)​

• It is now possible to run tests for releases. (packit/packit-service#2490)

Week 30 (July 23rd – July 29th)​

• packit pull-from-upstream now allows omitting upstream_project_url in the configuration in which case the interaction with the upstream repository is skipped during release syncing. (packit#2354)
• We have added the initial version of functionality for running scans in OpenScanHub. You can read more about this functionality here. (packit-service#2472)
• Added a new configuration option sync_test_job_statuses_with_builds that controls whether test job statuses are updated together with their corresponding build job statuses. When set to false, while tests jobs are waiting for their corresponding build jobs to finish, their statuses remain in pending state and only build job statuses are updated. (packit-service#2470)

Week 29 (July 16th – July 22nd)​

• We have implemented a CLI support for Koji builds against CBS Koji instance. (packit#2267)
• Added a new configuration option sync_test_job_statuses_with_builds that controls whether test job statuses are updated together with their corresponding build job statuses. When set to false, while tests jobs are waiting for their corresponding build jobs to finish, their statuses remain in pending state and only build job statuses are updated. (packit-service#2470)

Week 28 (July 9th – July 15th)​

• We have improved the babysitting of Testing Farm runs to better handle API outages. (packit-service#2464)
• We have adjusted commenting behaviour regarding Packit logs on release syncing PRs. (packit-service#2373)

Week 27 (July 2nd – July 8th)​

• Packit now updates its own, not yet merged, pull requests instead of creating new ones when syncing new releases downstream. (packit#2204)