codechecker icon indicating copy to clipboard operation
codechecker copied to clipboard
verified publisher icon Ericsson

Fix the PyPI job and ensure the package to-be-sent to PyPI is also tested appropriately

Open whisperity opened this issue 2 years ago • 2 comments

As mentioned in #3976, the PyPI job has been failing for quite some time now, and it is not possible to see if there are issues with only the PyPI package that otherwise do not surface in a locally created version. This should be rectified, but as a separate task, not to prevent the merging (and the subsequence working release) of #3976.

whisperity avatar Sep 26 '23 10:09 whisperity

I guess this the reason why https://pypi.org/project/codechecker/ still features 6.26.2 instead of 6.27.0 ?

amai2012 avatar Dec 09 '25 11:12 amai2012

@bruntib Should version 6.26.2 from pypi package work with a new server installation 6.27.x ?

amai2012 avatar Dec 12 '25 10:12 amai2012

Yes, this is a design decision that we'd like old clients be compatible with new servers as much as possible.

As for the pip deployment, we wouldn't like to push it immediately after release, because in case of a mistake, the deployment can't be undone with that version number. We are planning to automatize the deployment to test pypi, though.

bruntib avatar Dec 12 '25 12:12 bruntib