MyUW Processes and Practices - Apereo 2014

Apereo 2014 presentation about processes and practices in developing MyUW.

Transcript

1. Getting there is half the fun MyUW Processes & Practices Helwig • Petro • Vertein Open Apereo 2014 • Tuesday June 3rd
2. This presentation • Processes and practices of a long-established, sophisticated uPortal implementation.
3. See also • Last year’s presentation on Jenkins-driven Maven • This year’s presentation on MyUW Redesign • Tech demo of MyUW • Blog post version that will follow :)
4. Getting there is not in fact half the fun But thank you, Sam, for making the flight here not nearly as difficult as it could have been…
5. Themes • Automate everything • Have a process • Inspect and adapt
6. Meta • Licensed to you as CC-BY 4.0 , or • Apache 2 ; at your option ! • Opinions expressed herein are those of the presenter and not necessarily those of the University or of Apereo.
7. Context What are our processes and practices for?
22. Redesign
24. GitHub and pull requests
28. On looking both ways
30. Git / GitHub sure is nice • Pull requests • Branching • Merging • SourceTree / gitk
31. What happens without code review?
32. A story about overlays
35. Jenkins-driven Maven A recap of last year’s presentation
36. Source control
37. Our fork of uPortal
38. Our fork of uPortal
39. Overlays
40. Four server tiers • (Local development) • Predev • Test • QA • Production
42. Overlays on Overlays • Apereo provides a Notifications Portlet • Wisc has an overlay on that (the MyUW Notifications Portlet) • Each tier has an overlay • Declaring version of the MyUW Notifications Portlet • Tier-specific special sauce, configuration, etc.
43. Entity files in source control • Per tier • Commit triggers import; “cron” in prod • db-import , not initportal • i.e., import does not delete.
44. Jenkins running Maven • Triggered on source code commit • Builds the changed thing • Builds the things that depend on the changed thing • Deploys the built things, or stages them for scheduled deployment
45. Jenkins Running Maven
46. Jenkins Running Maven
49. Chatting with Jenkins
51. Nexus • Institutional Maven repository • Institutional cache of Central • Artifact repository management essential to a Maven-driven-Maven build strategy.
52. Scrum A set of processes and practices implementing a specific agile method.
53. MyUW Scrum • 2 Product owners • 3+ current Scrum Team members (Tim, Tim, Andrew), + student employee, + web developer • 2 week iterations
56. Definition of done
57. What does done mean? • Reviewed? • Refactored? • Performant? • Usable? Accessible? • Proposed upstream? • Merged upstream? • Tested? • Test cases? • Automated tests? • Unit? • Functional? • Integration?
58. Technical debt • Okay, it’s done for some meaning of done. • But it’s not done for some other meaning of done. • (Note that this is necessarily true no matter what you decide done means for you.) • So now you have technical debt. Maybe a little. Maybe a lot. • And eventually Codethulu awakes from its deep slumber and eats you and your team.
59. Certified ScrumMaster Training Recommended. http://www.collab.net/content/jimi-fosdick-cst
60. Migration
61. Migration Board
62. Kanban Or at least a few lists.
63. Server Admin Board
64. UX Design Trello board
65. Working with others Beyond the University, through Apereo
66. #jasig-uportal • We hang out in IRC chat • (We also hang out in Wisconsin-internal WiscChat) • IRC chat once again logged, now to echelog : • echelog.com/logs/browse/jasig-uportal/
67. uportal-[user|dev]@
68. Relating MyUW to uPortal • MyUW is a fork of uPortal • Merge Jasig/uPortal/master to MyUW/uPortal/uw- master as needed and at Jasig tags • MUM changes also usually go into Jasig/uPortal/ master, and then need merged / conflict-resolved back into uw-master • Even with git magic, this is kind of painful and friction-adding
69. When to pull request? • Code reviews are good. Pull requests are good. • How many to do where? • Pull requests within the team are good. • Pull requests in the context of the open source project are good.
70. Open, public repos • Environment-specific overlays are private • Non-environment-specific MUM stuff is mostly public • MUM uPortal repo being an exception (?) • Public repos make communication and collaboration easier
71. Using Unicon support • Validation of CONFIG permission issue and fix • Advice about avoiding layout corruption • Nailing that Tomcat session management bug
72. Inspect and adapt
73. Recent tweaks • Clarify “rule of two” for pull request merging • Introduce a Product Owner JIRA project / queue
74. Portlet Development Guide
75. Ideas to reduce friction • Engineer the adoption process • Dependencies and overlays (?) rather than forking • Engineer the uPortal source and build • Smaller, cohesive components with well-defined relationships via APIs • Automation, frequency for releases • Monthly patch release and yearly feature release?
76. Enabling web developers • Switch to natural template technologies? • Reduce reliance on XSLT? • Capture HTML snapshots for web developer to work with? • Move towards a JSON / rich JavaScript UI architecture (AngularJS?)
77. Take home points • Automate • Be mindful of process • Frantic email is not a process • Work in and with Apereo and open source communities to the advantage of your project • Inspect and adapt
78. Remember what’s important Getting there is half the fun when you are mindful about how you are getting there.
79. Photo acknowledgments • Scrum : https://www.flickr.com/photos/cdm/ 2336025560 • Steak : https://www.flickr.com/photos/jhpope/ 253041862 • Migration : https://www.flickr.com/photos/usfwshq/ 6777513684 • To do : https://www.flickr.com/photos/courtneyrian/ 5750960959