Download as PDF, PPTX
Uploaded byAtlassian
Slam Dunk with Splunk and Stash Data Center
The document discusses the challenges faced before and after the implementation of Stash by Splunk, highlighting issues like a non-scalable release process and network problems. It outlines the improvements made post-implementation, such as a 4x increase in code reviews and better collaboration. Key takeaways emphasize the importance of preparation, teamwork, and utilizing the best tools.
More Related Content
Similar to Slam Dunk with Splunk and Stash Data Center
Slam Dunk with Splunk and Stash Data Center
- 1. Slam Dunk withSplunk and Stash Data Center KURT CHASE • DIRECTOR OF RELEASE ENGINEERING • SPLUNK • @SPLUNK CHRISTOPHER PEPE • DRAGON OF THE WEST • PRAECIPIO CONSULTING • @PRAECIPIO
- 2. CHALLENGES BEFORE STASH IMPLEMENTATION AFTER STASH Agenda AFTERSTASH WHAT’S NEXT
- 3. CHALLENGES BEFORE STASH IMPLEMENTATION AFTER STASHAFTERSTASH WHAT’S NEXT
- 4. Less than Agile Legacy Non-scalable UnstableRelease Process Before BitbucketStash
- 6. Why Change? Atlassian Stack Issues withPerforce Faster Delivery Cadence Git
- 7. CHALLENGES BEFORE STASH IMPLEMENTATION AFTER STASHAFTERSTASH WHAT’S NEXT
- 8. ITEM 2 ITEM 1 ITEM3 ITEM 4 Agenda
- 9. Challenges Lots of Re-toolingWork Plan & Manage Everything Engineering Culture Change Access Control
- 11. CHALLENGES BEFORE STASH IMPLEMENTATION AFTER STASHAFTERSTASH WHAT’S NEXT
- 12.
- 14.
- 15.
- 16.
- 17. CHALLENGES BEFORE STASH IMPLEMENTATION AFTER STASHAFTERSTASH WHAT’S NEXT
- 19. Developer & ReleaseCadence Network Issues Biggest Blockers
- 20. CHALLENGES BEFORE STASH IMPLEMENTATION AFTER STASHAFTERSTASH WHAT’S NEXT
- 21.
- 22. 4X Increase in CodeReviews Completed
- 23.
- 24.
- 25. Top 3 Takeaways •Prepare well. • Have a good team. • Use the best tools.
- 26. Thank you! KURT CHASE• DIRECTOR OF RELEASE ENGINEERING • SPLUNK • @SPLUNK CHRISTOPHER PEPE • PARTNER & SENIOR SOLUTIONS ARCHITECT • PRAECIPIO CONSULTING • @PRAECIPIO