Skip to main content

· 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)

· One min read
František Lachman

Week 24 (June 11th – June 17th)​

  • We have fixed a bug that caused inconsistency between the promised environment variables (from the docs) and the environment that has been actually provided. Now you should have access to PACKIT_UPSTREAM_REPO and PACKIT_DOWNSTREAM_REPO (in case of propose_downstream and pull_from_upstream jobs), in the post-upstream-clone action. (packit#2327)