Skip to main content

8 posts tagged with "July"

View All Tags

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

Week 31 (July 28th – August 3rd)​

  • There is a new configuration option skip_missing_branched_composes that, when enabled, skips test jobs for freshly branched Fedora versions that don't have a corresponding Testing Farm compose yet. (packit-service#3160)
  • A fix has been implemented for a bug causing Packit to crash when adding a comment reaction on GitLab. (ogr#995)

· One min read
Nikola Forró

Weeks 29 and 30 (July 13th – July 27th)​

  • The ogr library now correctly handles the Forgejo error commit flag, resolving an issue that previously caused it to fail during internal mapping. (ogr#991)
  • Log Detective run overview on the dashboard now, for successful runs, shows also a list of snippets, grouped by file, in expandable sections. (dashboard#540) Log Detective snippets

· One min read
Nikola Forró

Week 27 (July 1st – July 7th)​

  • When a package is configured to consume mutiple release streams and release-monitoring.org detects multiple releases at the same time, if a pull-from-upstream job run for one released version fails, only that one is retried and the rest are unaffected and properly processed. Before this fix it could happen that a failed job run for one released version could prevent other released versions from being processed at all. (packit-service#3147)

· One min read
Matej Focko

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)

· One min read
František Lachman

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)