than 15 years we have been optimizing legacy systems of our customers • Modernization strategy • Replatforming • Set up test infrastruktur • Migration including automated transformation www.splendit.at jSparrow automatically facilitates your routine work with maintenance of important programs • Refactoring of legacy Java code • Eclipse, Maven and Github • Enhancement of code quality • Enforcement of company standards www.jSparrow.eu With our experience in old and new languages, we build bridges between existing technologies and new requirements.
◦ 2/3 of life cycle costs ◦ keeps business processes running ◦ legacy systems are SW assets • Daily Problems ◦ Too many other projects ◦ Limited resources ◦ Changing technologies and trends ◦ increasing technical debt ◦ “Never change a running system?” SW Maintenance References University of Houston: http://sceweb.sce.uhcl.edu
not only analyses Java sources - but automatically fixes issues and decreases technical debt • Mission critical – only safe changes performed ◦ some sonar issues are false positive • Chain of related rules - one rule creates input for following rules f.e.: Replace For-Loop with Enhanced For Loop => Replace For-Loop with Stream::forEach => Replace Expression Lambda with Method Reference • Categories of improvements ◦ Java 8/9/10 enhancements ◦ performance ◦ readability ◦ standards • User guided (Eclipse IDE) • runs on workstation and server
git-download your Jenkins-sources into Eclipse • Run SonarQube on these original Jenkins sources ◦ Run light-tests profile before jSparrow changes • Run jSparrow: ◦ Select sources ◦ Select 52 rules (including logging rule, excluding renaming rule) ◦ Summary page ◦ Apply changes • Run light-tests profile after jSparrow changes • Test Jenkins functionality after Code Refactoring and Modernization
git-download your Jenkins-sources into Eclipse • Run SonarQube on these original Jenkins sources ◦ Run light-tests profile before jSparrow changes • Run jSparrow: ◦ Select sources ◦ Select 52 rules (including logging rule, excluding renaming rule) ◦ Summary page ◦ Apply changes • Run light-tests profile after jSparrow changes • Test Jenkins functionality after Code Refactoring and Modernization
KPIs of refactoring Jenkins: • 166.870 - LOC in Java • jSparrow results: • 10.806 - issues fixed • 3 minutes 01 second – jSparrow execution time • 81 days 5 hours 01 minute - total saved time fig: Run Summary - jenkins core
did jSparrow improve Jenkins: ◦ Automatically refactored 10.806 issues (See our results) • How can you improve your code with Jenkins and jSparrow ◦ Integrate jSparrow into your maven build ◦ Define your ruleset in a YAML ◦ Define your profile in a YAML ◦ Run jSparrow in your builds Fits in multiple infrastructure!
still correcting your code manually ? • When do you start to jSparrow your Code ◦ Automated ◦ User guided ◦ Safe ◦ Fast, faster, jSparrow ◦ Integrated into • Eclipse • maven/github – including Jenkins build Don´t lose time with tedious and repetitive work – let jSparrow do it! Want to see it live?! Meet us at booth # 13 Just 3 minutes for a proof!!