on 2024 Oct 08 4:39 AM
Hi Gurus,
We developed our custom ABAP packages under our namspace and implement it to our customer systems.
At the moment the way we are managing and distribute fix to our customer is manually by making local changes in customer dev systems. (Weekly collect & categorize issues in customer systems, make changes in our central dev system and distribute the same to other customer systems.. All those changes are now being managed on JIRA). But this method seems not efficiently when the number of customers inscrease more and more.
I would like to ask if any methodology/tool to manage and distribute our fix/update to the customer. What is the best practice can support that?
Hope to hearing from you..
Thank you,
Kenny
Request clarification before answering.
Hi Graham,
That's a nice idea. we also thought about that.
But would there be any concern from customers about security or something that may come?
Do you have any advice on how we can convince customers to trust that method 😉
Thanks,
Kenny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would point out to the customer that using Git for code management has got to be safer and more secure than relying on a developer to manually copy code from one place to the other.
I would also point out that using a tool to update ABAP artefacts in your development system is no different to having a developer do the same thing.
And finally, if using Git for code management is good enough for their non-ABAP development teams (which it almost certainly is) why isn't is good enough for the ABAP team?
😎
User | Count |
---|---|
84 | |
29 | |
9 | |
9 | |
8 | |
8 | |
7 | |
6 | |
6 | |
6 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.