# Chocolatey Checksums Mismatch in CI Procedures

**URL:** <https://forum.ansible.com/t/chocolatey-checksums-mismatch-in-ci-procedures/35245>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [May 28, 2021, 10:34am UTC](https://forum.ansible.com/t/chocolatey-checksums-mismatch-in-ci-procedures/35245 "2021-05-28T10:34:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roy\_Keret](https://avatars.discourse-cdn.com/v4/letter/r/22d042/32.png) [@Roy\_Keret](https://forum.ansible.com/u/Roy_Keret)\
**Post date:** [May 28, 2021, 10:34am UTC](https://forum.ansible.com/t/chocolatey-checksums-mismatch-in-ci-procedures/35245/1 "2021-05-28T10:34:40Z")

</div>

Hi guys,  
In my company, we’re using the win\_chocolatey module to install several Windows programs as part of the CI process.  
Every now and then, a Chocolatey package gets updated while the checksum does not, resulting in the checksums mismatch, the win\_chocolatey failing and then failing our entire CI (40 machines?).  
To me it seems unmaintainable to allow all the CI to fail due to a temporary Chocolatey issue.

I’m trying to understand how I can mitigate the issue.  
I thought of several options:

1. Choose to ignore checksums altogether.  
Cons: I guess this isn’t best practice, security wise.
2. Specifying a version for the Chocolatey packages.  
This is assuming that old versions don’t have their checksums change.  
Cons: You’re not installing latest, then again, do you really care if you’re installing latest 7zip or a 2-months old 7zip?
3. Ignoring errors in win\_chocolatey  
Cons: Doesn’t sound feasible, assuming that all of these packages are needed for the CI process.