This week we focused on infrastructural topics. First we migrated more content from our old Liferay blog to WordPress. Then we created subdomains for some of our services.
Matthias also improved the blob server. Now it is possible to upload files up to a size of 500 KB. A generated URL can be used to download a specific file afterwards. This feature shall be enhanced by generating QR Codes that can be used by our app Lymbo.
Matthias cannot be here today so the last few steps of our model boat project must wait until next week. Instead the documentation of the app code could be generated automatically.
During this session we took a brake from working on our model boat project. This is partly caused by the explosion of model boat remote control…
We concentrated on our build processes which we want to use for Android and Raspberry alike. Today we focussed on deployment of Android apps. For that reason we installed fdroid on our server. Fdroid can be used as a Android repository for binaries as well as sources. Using the fdroid app we can receive the latest version of all apps we are working on.
Android app deployment automation
Whenever someone pushes any changes on an Android app to the source code management system a job on our continuous integration system Jenkins is triggered. This job fetches the latest sources and builds an Android apk file. After that the Jenkins job copies it to our fdroid repository and updates it.
The robot soccer team Tigers Mannheim will take part in Robocup 2013 Eindhoven. As in the last two years they will compete in small size league against the best teams from all over the world. Visittigers-mannheim.de/ to get more information about the team. Let’s go, Tigers, let’s go.
This Thursday we will not work on our model boat project together. Our next appointment will be on June 20 2013. Stay tuned.
Jenkins is a continuous integration tool which can be used to automate processes. This contains building, deploying, testing and whatever you could do manually. It allows for defining jobs that can be triggered manually or automatically. These jobs can contain shell or DOS code or even ant scripts.
Jenkins runs on our Debian server and can be configured and monitored via a web interface. One great feature is to connect Jenkins with SVN which we chose as our version control system. Jobs on Jenkins can checkout a local working copy of SVN repositories and work on. Furthermore it can trigger jobs when SVN has changed.
Deployment of Liferay Plugins
We built Jenkins jobs that checks out Liferay Plugins from SVN into the Jenkins workspace. One plugin will be copied into the PluginsSDK environment of a specific Liferay instance where the build will be triggered by an ant script that also deploys the plugin into the Liferay instance.
Deployment of Android apps
One of our Jenkins jobs checks out the sources of an android app from SVN into the Jenkins workspace and builds the apk file afterwards. For this purpose the Android SDK version needed for the this app must be installed on the server. After the apk file is built it will be copied to our Owncloud cloud device. Every developer Android device using the Owncloud app has access to this new built app.