Skip to main content

A month of Flutter: configuring continuous integration

Republished from with permission.
When starting a new project I like to automate as much as possible. One of the most important tasks is getting tests running on CI. There are a number of great CI services but for this project I'm going with Travis CI.
Let's take a look at the configuration I've settled on and what it all means:
language: dart
dist: xenial
      - lib32stdc++6
  - git clone -b beta
  - ./flutter/bin/flutter doctor
  - cd app
  - ../flutter/bin/flutter test
    - $HOME/.pub-cache
  • language tailors the CI environment for a specific language. If you leave this out, the default language is Ruby. This isn't strictly needed as Flutter will actually download its own version of Dart. I specified Dart so that if I write CI tooling in the future, I can do it in Dart.
  • dist specifies the Ubuntu base version that gets used. Travis currently defaults to Trusty Tahr which is end of life in 2019 so I'm specifying Xenial Xerus which is supported until 2021.
  • addons lets you have additional packages installed on the OS. In my experimentation, tests still pass without lib32stdc++6 but flutter doctor complains so I'm including it anyway.
  • install would typically call Dart's pub get but Flutter complains so we'll just override that and install Flutter instead.
  • script is where we run the tests. Not that the Birb app is in the app directory so we have to cd into it first.
  • cache is the final bit. This tells Travis to cache the contents of the default Dart package cache. This should make it faster for Flutter to install the app's dependencies.
This configuration runs great and takes about 2 minutes 30 seconds on the base app.
I also tried caching the flutter directory to boost install speed. Here is an configuration iteration I tried:
  - |
    if [ ! -d flutter ] ; then
      git clone -b beta
  - ./flutter/bin/flutter doctor
    - flutter
    - $HOME/.pub-cache
Caching the flutter directory dropped the test run time to to about 1 minute 10 seconds! The install step was then more complex as it has to check if the flutter directory exists and only run git clone if it doesn't. But there was a larger issue where the "if directory does not exist" was having false positives and causing Flutter to not get installed correctly. I would like to improve CI performance but don't want to spend any more time on it now so I've added #6 Cache flutter directory on CI to the backlog as a future improvement.
With CI setup, I like to protect the master branch from accidental pushes. This is less important when you are working on your own but is very important when working with teams. It's also a good way to require that tests are kept in a passing state.
This is how I configured GitHub's branch protection on the master branch:

Come back tomorrow when I'll setup linting.

Code changes


Popular posts from this blog

CloudSense: the Future of Advertising

With the whole cloud taking off and more and more services switching to a push it into the cloud, leave it there until you need it, and pull it out model. I can only imagine what will be switching to this model soon. Oh wait. I can imagine.


Reading an article about how Avril Lavigne is supposed to have a $2 million check "appear" in her mailbox because of the absurd number of streams her videos get from YouTube got me thinking about creator compensation. The problem Avril is having is, a) Google wants to keep the money, and b) Google is having trouble figuring out how to monetize video streams. But on a grander scale it is whoever puts the ads on the page that gets the money not the content creator.

Little known @Twitter and @TwitterAPI tips and tricks

Be sure to comeback as new tips and tricks get added. If you know of anything I missed be sure to let me know.

Static URL for profile images based on screen_name:

* This performs a http redirect to the actual profile image URL. Currently https redirects to http. You can also add "?size={mini | bigger | normal}" to get specific sizes.

Redirect to profile based on user_id:

In_reply_to_status_id mentions:

* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.

Profile image sizes:

* By default you get the original image size you can add _mini, _normal, and …

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empt…