Skip to content

use admin ci to update trunk checksum

Menglin Xu requested to merge mexu_admin_ci_update_trunk_checksum into master

Enhance checksum verification tool

new procedures

Developers should never be including modified checksum files for whatever trunk version or released version in their committed changes. If the changes in a merge request will change the checksum in trunk version, maintainers can use update-trunk-checksum label to update the checksum. First select update-trunk-checksum label, then trigger a new pipeline. Afterward, you will see an options button in the pipeline. Next, remove this label, click the button, then the bot will help us update the checksum files in the trunk version.

changes:

  • optimize the checksum python script to give more information.
    • if the checksum verify test is failed for version, throw the message: the chekcum for verions can not be changed, please check
    • if truck checksum ci test is not passed, say, please not update it by yourself, pin maintainer to do that before mergin
  • add a check in the pre-commit to enforce that the checksum files are not included in the change-set
  • introduce an admin CI to allow maintainers to update the trunk checksum in a request before merging
  • Update doc/HOWTO.md according to the new policy of updating checksum

Validated by

  • Core Software
  • RTA
  • Simulation
Edited by Gloria Corti

Merge request reports