Mobile Application Lifecycle with Jekins, Trello and CollabNet TeamForge

Main sponsor

Mobile Application Lifecycle

Luca Milanesio

Who’s that guy ?

Luca Milanesio
LMIT Software / GerritForge LLP

Over 20 years of disruptive activity in the
Software Development Lifecycle

Jenkins CI contributor
founder of Jenkins-Mobi

Git enthusiast since 2009 and
innovator in large enterprises

Gerrit contributor since 2011, driving
plugin and ALM Integration

www. -ci.Mobi Copyright © 2013 – LMIT Software Ltd

Agenda

• Why are we doing this ?
• Agile lifecycle on Mobile Development
• One step forward to continuous delivery
• Mobile ALM in a real life experiment
• Beyond development … everything Mobile
• Call to action !


Why are we doing this ?

Who is a Mobile Application Developer ?

Who is working in a team ?

Raise your hand !


Anatomy of a typical (mobile) Project

Client (mobile) tier Server (cloud) tier
• Rich client UX • RESTFul API
• Multi handset (Android / • Multiple client support
iOS / WP8) (native versions, Web)
• Hybrid / Mobile Web UX • User authentication
• Local caching • Persistent storage


Why (mobile) Project is more complex ?

Client (mobile) platforms diversity is hell !!!


Lifecycle of a (mobile) Project


Is it really agile ?

Agile software development means:
1. Always working software through Continuous
Integration
2. Welcome change at any stage
3. Close daily collaboration with Business
4. Short loop of changes / feedback
5. Simplicity


Impediments in (mobile) Agility (1/3)

1. Complex client runtime environment
– Mobile Phones are not PCs
– Emulators <> real handsets
– Physical limits to Continuous Integration



2. Client / Server integration
– multi-Client with multi-Server versions
– Different Client vs Server environment
– Changes often impact multiple tiers



3. Client distribution / installation
– Native channels for distributing clients
(Google Play, AppStore, Windows Phone Store)
– Delay from built to deployed to handsets
– Problems in getting Business up-to-date


What would we need for extra agility ?

1. Real continuous delivery to real handsets

Cloud deploy

Change Build

Client deploy



2. Client upgrade and notification in real-time

One-tap
upgrade
Client Ver. X Client Ver. X+1



3. Bring all together in a single place

Cardwall
Client App
Ver. X

Changes Continuous
Integration

Issues Monitor


Hold on … don't we have that ?

john@mydomain.com
Cardwall
***************



john23@gmail.com

Monitor ************



Continuous
Integration



Issues


Cool … and if have two projects ?

"WTF WTF WTF WTF #$@#!%@$"
Clean-up data, re-configure,
scream and shout …
… and over again and again and
again !
My project is on local net …
tunnels, firewalls, VPNs, slow …
WTF WTF WTF !!!


We can do better !

1. No need to setup 4+ apps /
tools on stakeholders'
phones


We can do better !

2. One-tap access to any
Project Lifecycle item
(Story, Bug, Test, Build,
anything !)


We can do better !

3. Link stories to builds,
bugs, tests, results,
artifacts …
connect the dots to see
the full picture !


We can do better !

4. One set of credentials and
identity to rule them all,
inside or outside your VPN
!


We can do better !

5. Notify all stakeholders in
real-time about new Betas
and give "one-tap" upgrade
process !


Real life [experiment] story

The challenge: developing a Mobile App for
a Global Mobile Operator in 8 EU Countries


Center of the lifecycle: Continuous Integration

1. Monitor the SCM changes
2. Build the software
(Client, Backend)
3. Run unit-tests
4. Deploy backend to QA
… but one step was missing …
 Deploy client to handsets
with JenkinsMobi


Jenkins hits for Mobile
• Android build  Simple Ant with ADT
• Android unit-test  Android Emulator Plugin + monkey
(https://wiki.jenkins-ci.org/display/JENKINS/Android+Emulator+Plugin )

• iOS build  Xcode + SICCI plugin
(https://wiki.jenkins-ci.org/display/JENKINS/SICCI+for+Xcode+Plugin )


Build and install JenkinsMobi on Android

1. Build status 2. Build artifacts 3. Download 4. Upgrade


Adding sprints plans
1. Access Project Sprint Plan (TeamForge)
2. Access SCRUM sprint board (Trello)
3. Connect and display progress


Display Sprint status using JenkinsMobi plugins

1. Sprint progress 2. Cards status 3. Cards list 4. Cards details


Monitor acceptance tests in real-time
1. Display test plan execution (HP QC)
2. Monitor incidents during QA (HP QC)


Check QA status using HPQC JenkinsMobi plugin

1. Test progress 2. Test results 3. Defects progress 4. Defects list


How [we] and YOU can do it ?

Private Network

1. Get a Mobile 2. JenkinsMobi 3. Connect to 4. Plug to your
Phone on board JenkinsCloud ALM Tools


Wrap-up and achievements

1. Project delivered on-time
2. Lots of suggestions from all stakeholders
(Product owner, QA, markets, developers)
3. Shorten the E2E feedback loop
Problem  Ticket  Fix  Re-test
4. Early risk management of delays and
changes


JenkinsMobi vision

1. Mobile is the 21st Century Web 3.0
2. Development will be more and more
Mobile-centric
3. Mobile is the center of the Team
Cooperation
4. Continuous Integration is the center of
the Development loop
5. All tools can be "plugged" into the Mobile


Call to action !!
• JenkinsMobi is in your pocket !
33rd Degree App is JenkinsMobi
v4
• Start using Jenkins at the
center your Mobile Application
Lifecycle
• Extend JenkinsMobi with
OpenSource plug-ins


JenkinsMobi v4 – 2013 road-map

Mar/Apr  Private Beta
- All existing JenkinsMobi v3 features
- Support for private Jenkins / plugins on VPN
- Jira and Trello plugins
- PingDom plugin
May  Global upgrade from v3 to v4
June  JenkinsMobi plugins specs opened
- JenkinsMobi Cloud OpenSource
- JenkinsMobi Plugins OpenSource specs


Resources

Contact Luca Milanesio at:
luca@jenkins-ci.mobi
Twitter: @gitenterprise | Facebook.com/gitenterprise
Blog: gitenterprise.me
About JenkinsMobi:
http://jenkins-ci.mobi
Twitter: @hudsonmobi | Facebook.com/jenkinsmobi
Blog: jenkinsmobi.me
Replay this slides again at:
http://slideshare.net/lucamilanesio
market://details?id=com.lmitsoftware.app33degree


Mobile Application Lifecycle with Jekins, Trello and CollabNet TeamForge

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (13)

Similar to Mobile Application Lifecycle with Jekins, Trello and CollabNet TeamForge

Similar to Mobile Application Lifecycle with Jekins, Trello and CollabNet TeamForge (20)

More from Luca Milanesio

More from Luca Milanesio (18)

Recently uploaded

Recently uploaded (20)

Mobile Application Lifecycle with Jekins, Trello and CollabNet TeamForge