-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve patchComponent script #11685
Comments
@todor-ivanov I think you have worked on this script this quarter, didn't you? Should we close this issue out? If your changes to patchComponent.sh already closed an issue, then please close this one as "Not Planned" |
hi @amaltaro , yes I have it all fixed.... and in addition I have one more script to deliver - one which would allow a full K8 cluster patch on the fly - either by |
Perhaps these scripts should be placed under https://gitlab.cern.ch/amaltaro/wmcore-tools ?? |
only now I realize the BTW, those are under bin - because it is helpful to have them in the WMCore auxiliary code and the environment which we are working in rather than constantly downloading the scripts from some repository before patching. and also with the virtual environment - anything that is in |
Impact of the new feature
Operations
Is your feature request related to a problem? Please describe.
While working with this issue: #11157 I had to patch my WMAgent back and forth multiple times with several patches, in order to test the newly provided changes. In general for such purpouses I use the following script: https://github.com/dmwm/WMCore/blob/master/bin/patchComponent.sh But this script
All this requires a lot of operational effort especially when it needs to be done on the agent multiple times and it is extremely error prone an difficult to keep track of what is patched at what moment.
Describe the solution you'd like
Add the above described features
Describe alternatives you've considered
Manually do the work every time and risk to break the component during development or loose track and not being aware of what exactly is currently under test
Additional context
none
The text was updated successfully, but these errors were encountered: