Last modified: 2014-04-11 09:51:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65765, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63765 - Setup automated builds for the Android app
Setup automated builds for the Android app
Status: NEW
Product: Wikipedia App
Classification: Unclassified
Automated Builds (Other open bugs)
Android (alpha)
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-10 13:06 UTC by Yuvi Panda
Modified: 2014-04-11 09:51 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Yuvi Panda 2014-04-10 13:06:45 UTC
Android based building with jenkins is broken atm and would need to be setup properly.
Comment 1 Antoine "hashar" Musso (WMF) 2014-04-10 13:10:17 UTC
So I manually installed the Android SDK ages ago on the gallium server. There is a single job using it and the label is only applied on gallium:

 https://integration.wikimedia.org/ci/label/hasAndroidSdk/?

Job is: https://integration.wikimedia.org/ci/job/apps-android-commons-build/

It fails because the Android SDK is unsurprisingly out of date.


Uubuntu Trusty apparently has a package for android SDK http://packages.ubuntu.com/search?keywords=android (and a recent one 2014 03 28).  It might be possible to install that package on a Precise Ubuntu. If that works we can get ops to add the package to apt.wikimedia.org then have it installed on the labs slaves and problem is solved :]

Else we will have to figure out with ops if that package can be backported to Precise. If it is not possible we will have to find another solution.

You could try installing the trusty version on a labs instance and see what happens :]
Comment 2 Yuvi Panda 2014-04-10 14:22:51 UTC
The package from trusty does not have the android SDK. It had a bunch of android images, and that is it. I don't know what it is supposed to be used for.
Comment 3 Yuvi Panda 2014-04-10 14:23:21 UTC
Ah, apt-cache tells me they are:

android - android Ubuntu Touch images
Comment 4 Antoine "hashar" Musso (WMF) 2014-04-10 15:38:51 UTC
So that is probably useless for us isn't it ? :-)

Could you figure out how one can install the Android SDK manually? Then poke ops to hopefully have that puppetized.  At worth it can be a shell script.
Comment 5 Yuvi Panda 2014-04-10 18:16:59 UTC
So https://gist.github.com/yuvipanda/10408391 installs the latest version of the android sdk and installs it in home.

Unfortunately on Ubuntu 12.04 it requires other packages to work. 

I've managed to get this to build on tool-labs as a one off, but to actually work properly even on toollabs it requires  https://gerrit.wikimedia.org/r/125241 to work. Android sdk still isn't natively 64 bit fully, so that is a problem.

But with all that it works! Perhaps we can make a contint labs instance that is used just for this? Also note that the shell script to setup the SDK needs to be run only once
Comment 6 Antoine "hashar" Musso (WMF) 2014-04-11 09:51:39 UTC
(In reply to Yuvi Panda from comment #3)
> Ah, apt-cache tells me they are:
> 
> android - android Ubuntu Touch images

That is not the package we need.  The Debian source package androidsdk-tools seems to generate a bunch of binary packages that might be more interesting. See list at https://packages.debian.org/source/sid/androidsdk-tools


We might backport them from Ubuntu Trusty to Ubuntu Precise https://packages.ubuntu.com/androidsdk-tools :-]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links