Update rucio-clients version from 1.25.5 to 1.29.10 #11368
Conversation
|
Jenkins results:
|
|
Jenkins results:
|
Update CMSMonitoring from 0.6.9 to 0.6.10
|
Jenkins results:
|
|
unit test failures are unstable, so not really an issue here. |
There was a problem hiding this comment.
Changes are fine to me but may be we can save time if we'll use only two digits match, e.g. instead of rucio-clients~=1.29.10 we use rucio-clients~=1.29. If I'm not mistaken it will pick up all versions from 1.29, and therefore we'll not need to change our requirements if new version from this major tag is released. Just think about it.
|
That might be an option for the future indeed. However, I think I still prefer to have a better control of the software stack packaged with WMCore services. We have some many python libraries - and inner libraries - that I am always concerned that even a minor release change can break things for us. In addition, we usually do not update python libraries based on their minor versions. Last update for rucio-clients has been last year (hence the large jump from 1.25 to 1.29). |
Fixes #11359
Status
not-tested
Description
This pull request updates the python
rucio-clientspackage to the latest stable release,1.29.10.It also brings in
cmsmonitoringfrom 0.6.9 to 0.6.10 (to resolve a dependency conflict with jsonschema)As usual, a few inter-dependent libraries get updated as well.
Is it backward compatible (if not, which system it affects?)
MAYBE
Related PRs
None
External dependencies / deployment changes
cmsdist spec: cms-sw/cmsdist#8196
UPDATE: there are hard dependencies on the cryptography library and changes to the manage script are required, please see #11378 (comment) for further details.