h

Bruno Verachten

Tinkering Padawan

GitHub
Medium
LinkedIn
BIO

Father of two, husband of one, geek in denial, fond of handheld devices since 1989, beekeepeer and permie. #Linux #Android #Docker #ARMV8 #IOT
Joined Worldline in 1999.
Currently works as an continuous integration for mobile development specialist.
Fond of Linux and open source, hand-held devices (SBC…).
Also interested in new techniques in gardening, woodworking by hand, bike commuting and tons of other subjects.
Disguised as taciturn, but a chatterbox.

Trying to push the use of ARM Socs in his job and everywhere else…

TALK 1

The Android device farm that fits in an (cloudy) pocket

Android developers are facing a common problem: how to test our applications on many devices without sacrificing too much time or money?

  • How to build and test automatically our applications for each commit?
  • How can we find those devices inside the company, whatever its size may be?
  • Could there be a directory somewhere that lists those available devices?
  • Could we use a device remotely and share it with other developers as if it were in the cloud?

What if you could answer all these questions with the help of a low cost device farm that fits into a pocket? A pocket full of clouds…

Poddingue, our proposal, aims to tackle this problem thanks to Docker, HypriotOS, Armbian, Gitlab CI and OpenSTF. It’s an internal solution made of OSS readily available, but it has not yet been publicly announced as a whole.

This presentation won’t be too technical ; it is opened to anybody who has an interest into Android, exotic hardware or continuous integration, as long as you can stand a bad sense of humour. At the end of the talk, you should know how to build your own cloudy pocket farm of Android devices and how to use it to test your applications within your ci pipeline.

And as I am cheap, you will also be surprised at how little money you need to build it.

TALK 2

???? ARM your continuous integration system with fruits! ????

Being able to build/test/deploy on a remote machine each time we commit has been a major progress for us, developers. ???? Furthermore, by using Docker, things have been so much easier! No more dependency hell when you have to build and test two incompatible products. This solution looks almost perfect… until you reach a threshold. As your Gitlab-ci will become more and more popular within your organization, you may experience longer waiting queues until the next batch of Runners is released. You maybe have a Raspberry Pi taking dust on your desk or in your drawer. What if I told you you could transform this momentarily useless piece of hardware into a brand new Gitlab-ci Runner? This way, you could shorten the time your jobs spend in the queue. But wait, there is more. What if there was a cheaper solution that could allow you to create a Gitlab-ci Runner for a 15€ investment? You may have heard about Banana Pi, Orange Pi, and other variations of fruit Pi(e). The competition is harsh between these manufacturers, and you can find pretty nifty machines for darn cheap. These machine can run Docker, and even Gitlab-Runner on top of it. What if you could even build Docker images through CI on these machines? Is this even possible? It is. You shall leave this talk by knowing the basics to start your own Gitlab Runner for 15€.

Valli Ravindran
Menu