Tom S Rodman TSRodm@gmail.com Milwaukee, WI cell: 414-678-9284 ll: 414-486-1207 (no voice mail/best for interview) Dear valued employer: Was a co-member of 2 person team migrating Jira, Confluence, Bamboo, and Crowd from Walgreens datacenter to CatalystRX datacenter. Experienced in initial setup and migration of Atlassian tools under RHEL Linux - Jira, Confluence, Bamboo, Subversion, and Crowd. UNIX scripting and administration experience since 1988, GNU/Linux experience from 1996. About 25 years supporting: software or hardware development, UNIX servers and engineering applications. ~2720 total Linux/UNIX system administration hours over those years. US citizen; available immediately; will relocate within 100 miles of Milwaukee WI 53207. Latest/up to date resume; hours of focused work by skill; code samples: ( www -dot- trodman -dot- com ) Jira/Atlassian Experience: - our server at CatalystRX had a highly customized set of jira workflows; jira w/confluence and the other Atlassian tools, constituted a mature collaborative SDLC (java development) - one of two on SCM team at CatalystRX w/jira and confluence administrator rights, and Atlassian support accounts - multiple fresh installs/configs of jira, confluence, crowd, and Collabnet svn done; worksteps documented in detail - together w/project lead developed method, and tests for the process of: migrating jira and data to our new server/datacenter - maintained, monitored, tested cron driven jira and confluence backups - jira log monitoring, log parsing during troubleshooting, and known good states - jira workflow-change testing - maintained/enhanced, jira-triggered EAR 'scp' perl script - wrote and regularly used several python and bash script wrappers (utilities) around jira.sh, and confluence.sh - multi-year experience, day in day out "end user" of jira, confluence, bamboo, svn... - beginner level familiarity w/new jira workflow setup - Loaded and tested jira workflows on my PC. Spent about 16 hours studying jira workflow creation. - spec'd out vm Xeon hardware for jira, confluence, bamboo, crowd Linux servers My Atlassian experience was with Walgreens Health Initiatives, a piece of which became CatalystRX, then Catamaran. While I was there, they migrated from cvs to svn, and at the same time completely redesigned their Software Design Lifecycle around jira project enhancement/fix, and build/deploy workflows, linked to collaborative confluence wiki pages, and documents. This was under Centos/RHEL, and AIX (websphere). I watched them develope a series of developer (and many other project roles) training classes, and I did one short presentation on 'make' builds. Bamboo was used for ant java builds (99%), and a couple make driven C++ builds. They had two java developers (consultants from http://www.herzum.com/) that helped in depth jira customization, that I got to know personally- for the first 1.5yr or so one of these also took primary sys admin responsibility for Atlassian tools, but I helped him w/Linux system admin. Also I worked on to migrate jira, Confluence, Collabnet svn, Fisheye, and Crowd from a single 8 core server in one data center to another datacenter but on multiple xeon core VMs. In that process I installed jira, bamboo, crowd, svn, and confluence; assisted and troubleshot an issue in a few trial migrations of jira, svn repo, and Confluence. -- thanks/regards, Tom S Rodman TSRodm@gmail.com