Automating Software Releases (Dallas/Ft. Worth Perl Mongers 2004)

Slide 1: Automating software releases brian d foy August 24, 2004 Dallas/Ft. Worth Perl Mongers sponsored by Metallect

Slide 2: Everyone’s problems • Software has problems • Problems suck time • Keep you from what’s important • It’s not just the code

Slide 3: Automate • Repetition • Dull bits • Discovery • Notification • Monkey work

Slide 4: Mechanics are easy • Mechanics are easy • Simple matter of programming • Solutions are not so easy

Slide 5: My problems • Many Perl modules • Forgot things • Didn’t run tests • Stale source control • POD errors

Slide 6: Heal thyself! • Find problems before users • Avoid embarrassment • Know on day -1 • Save time • Develop process

Slide 7: release(1) • Created a script • Used Perl • Started small • Got a bit ugly • Put on CPAN

Slide 8: Releasing is easy • Have software • Want other people to use it • Just give it to them

Slide 9: Oh no! • Did not test software • Missing files • Old information • People complain!

Slide 10: Preparing is harder • Squash bugs • Test code • Test distribution • Sync source control • Update information

Slide 11: Development Lifecycle • Specify • Design • Implement • Test • Accept • Release

Slide 12: Steps • One at a time • Requirements to move on • Check • Move on

Slide 13: Checking • Different  types  times  reasons • Automate it!

Slide 14: Distribute • Multiple uploads • Announcements • Automate it!

Slide 15: Computers can help • Use your computer! • Figure out  want  need  should • Script checks for it

Slide 16: Module::Release • Ken Williams refactored release(1) • Does the same thing • Write your own scripts  Chris Nandor • Add your own functions  Module::Release::Subversion

Slide 17: Module::Release 2.x • Easier • Pluggable • Shareable • Automatic • Not Perl specific

Slide 18: Future additions • Pre-flight • Tests • Distribution tests • Source control plugins • Upload plugins • Little language

Slide 19: The End