Yesterday I attended TDC.
It was fun to see so many from the software development community in Trondheim turn out all at once.
I also had a short talk about better ways to work, focusing on delays and feedback – especially how it’s more central to knowledge work than we think.
Here’s the slides if you’re curious (PDF):
201210 TDC Better ways to work
Update: I added a few slides for a talk at the office – see extended version (pdf) if you like, containing a few more links/ reading tips.
What is an operations review (ops review)?
To do an ops review is to take a look at your team or organization:
- driven by data
- involving management and business, up- and downstream in value chain
- look at the whole, i.e., all kinds of work
- look at both value/ benefit and cost
Why should you do ops reviews?
- create a culture of openness and trust
- create shared understanding across different stakeholders
- it’s about learning
- teaching senior exec’s about the business
I just got involved with a mobile project, and let my inner devop out for a moment… So, here’s how I got Jenkins to build, sign, and deploy an Android app for testing.
- Jenkins CI, installed on a virtual Ubuntu server,
- Android SDK on the Ubuntu server,
- Android SDK compoments (including an Android profile/ target),
- an Android project
- keytool on Ubuntu to create a simple keystore, for signing the app
The gist of the Jenkins job is:
- Get updated code from Git
- Execute shell command to create an ant build file on the fly with the Android SDK tool android:
/opt/android-sdk/tools/android create project -n [name of resulting app file] -t [Android target] -p [name of temporary directory where project is copied and ant files generated] -k [package] -a [default app class]
- Copy resulting build.xml from the temporary directory to the project root
- Run ant targets clean release, with the following properties:
- (Without the last four properties above the job will build an unsigned app)
- Publish resulting .apk via FTP to a server
And on my phone:
- Allow installing apps from unknown sources
I got useful info from an article on jenkins-ci.org: Getting started: Building Android apps with Hudson. My needs were a bit simpler, so you’ll see a bit more details there than here.
A few problems I had:
- The Ubuntu VM didn’t have X installed, and getting SDK components seems to require a GUI. I tried to go around this by copying tools and targets from SDK on my laptop.
- A bit later I got stumped by an error message on aapt and “no such file or directory”. (This might have been related to what I did on the previous problem…) An answer on stackoverflow regarding ia32-libs provided the solution in my case.
This project is a side project with low activity compared to a day job, so right now this job is a one-click deploy job (one click plus downloading and installing on the phone…) However, I think we’ll set up nightly polling, so there’s an updated app available every morning for testers, and they can see by the timestamp if there were any updates the previous day.