fledge 0.1.3

  • Readme
  • Changelog
  • Example
  • Installing
  • 51

pub package Build Status drawing

Fledge

See https://medium.com/@nocnoc/cicd-for-flutter-fdc07fe52abd for introduction to Fledge.

Fledge: A CICD tool for Flutter #

Automatically build, test, sign and release your Flutter app to both Apple and Google stores.

Supports public and private build servers in the cloud (Travis, Cirrus, etc...) and in-house (Jenkins, GitLab, etc...).

There are many steps involved each time an app, or an app upgrade, is delivered to both stores. Fledge exists to document and automate these steps.

Quick start #

For example, with GitHub and Travis:

  1. Install Fledge

     $ pub global activate fledge
    
  2. Add secrets
    Set your secret variables in:

     https://travis-ci.org/<your name>/<your repo>/settings
    

    secret variables
    These variables are used for signing and uploading to both stores.

  3. Add app to Fledge
    Install the Travis config file and Fastlane files

     $ fledge config -b travis
    
  4. Start a beta
    Run pipeline on Travis

     $ fledge beta
    

    This will build your app, upload to both store consoles and release to beta testers.

  5. Release to users

     $ fledge release
    

    This will release the app to users.

Documentation #

As with any mobile app, there are several one-time setup tasks (most of which you have to do anyway… even without a CICD tool).

To avoid having to gather together all the bits and pieces of information required to deliver a Flutter app, the Fledge project has created complete documentation to walk you thru all the setup tasks for the more common scenarios.

One of the reasons the Fledge projects exists is to document these one-time setup tasks and progressively automate them where possible (and then remove from documentation).

Fledge Docs

View the documentation site for complete usage and configuration information.

Demo #

For a demo of Fledge in action see: https://github.com/mmcc007/todo. Links are included to view the pipeline on Travis that delivers betas and releases to both stores.

The demo app was delivered automatically to both Google and Apple stores using a Fledge pipeline.

You can download the demo app to your android or iOS device:
GitErDone GitErDone

Fledge trace-back feature #

This feature allows you to track what version of your app is running on any device. Useful for support and bug-fixing.

To use the Fledge trace-back feature, tap on the app title 'GitErDone' to view the 'About'.

On an android device you will see:
android screenshot

On an iOS device you will see:
ios screenshot

You can then trace back to the Fledge pipeline that delivered the app (click on image below for link to actual pipeline):
fledge pipeline

License #

Fledge is distributed by an MIT license.

Contributing #

When contributing to this repository, please feel free to discuss via issue or pull request.

Issues and pull requests are welcome.

Your feedback is welcome and is used to guide where development effort is focused. So feel free to create as many issues and pull requests as you see fit. You should expect a timely and considered response.

Code of Conduct #

Fledge is committed to fostering a welcoming community.

Big Thanks #

Mobile Testing Platform and Open Source <3♥ Provided by Sauce Labs

0.1.3 #

  • Fixed provisioning profile name on iOS build

0.1.2 #

  • Removed local Fastlane dependency.
    Allows Fledge to run on macOS, Linux, and Windows.
  • Added example app demoing integration to build server.
    Demo runs on travis, and can run on other build servers.

0.1.1 #

  • Updated docs

0.1.0 #

  • Initial release

0.0.4 #

  • Resolved documentation generation issue

0.0.3 #

  • Provided required example and resolved documentation generation issue

0.0.2 #

  • Resolved package analysis issues

0.0.1 #

  • Initial version

example/lib/main.dart

import 'package:flutter/material.dart';
import 'package:flutter_driver/driver_extension.dart';

void main() {
  // Enable integration testing with the Flutter Driver extension.
  // See https://flutter.io/testing/ for more info.
  enableFlutterDriverExtension();
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or simply save your changes to "hot reload" in a Flutter IDE).
        // Notice that the counter didn't reset back to zero; the application
        // is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug painting" (press "p" in the console, choose the
          // "Toggle Debug Paint" action from the Flutter Inspector in Android
          // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
          // to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.display1,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Use this package as an executable

1. Install it

You can install the package from the command line:


$ pub global activate fledge

2. Use it

The package has the following executables:


$ fledge

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:


dependencies:
  fledge: ^0.1.3

2. Install it

You can install packages from the command line:

with pub:


$ pub get

with Flutter:


$ flutter pub get

Alternatively, your editor might support pub get or flutter pub get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:


import 'package:fledge/fledge.dart';
  
Popularity:
Describes how popular the package is relative to other packages. [more]
8
Health:
Code health derived from static analysis. [more]
95
Maintenance:
Reflects how tidy and up-to-date the package is. [more]
95
Overall:
Weighted score of the above. [more]
51
Learn more about scoring.

We analyzed this package on Mar 31, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

  • Dart: 2.7.1
  • pana: 0.13.6

Health suggestions

Fix lib/src/commands/config.dart. (-1.99 points)

Analysis of lib/src/commands/config.dart reported 4 hints:

line 34 col 3: The class 'Future' wasn't exported from 'dart:core' until version 2.1, but this code is required to be able to run on earlier versions.

line 67 col 7: DO use curly braces for all flow control structures.

line 71 col 1: The class 'Future' wasn't exported from 'dart:core' until version 2.1, but this code is required to be able to run on earlier versions.

line 80 col 1: The class 'Future' wasn't exported from 'dart:core' until version 2.1, but this code is required to be able to run on earlier versions.

Fix lib/src/commands/beta.dart. (-1.49 points)

Analysis of lib/src/commands/beta.dart reported 3 hints:

line 95 col 7: DO use curly braces for all flow control structures.

line 103 col 7: DO use curly braces for all flow control structures.

line 124 col 47: DO use curly braces for all flow control structures.

Fix lib/src/io.dart. (-1.49 points)

Analysis of lib/src/io.dart reported 3 hints:

line 676 col 5: Future results in async function bodies must be awaited or marked unawaited using package:pedantic.

line 866 col 3: Future results in async function bodies must be awaited or marked unawaited using package:pedantic.

line 867 col 3: Future results in async function bodies must be awaited or marked unawaited using package:pedantic.

Fix lib/src/error_group.dart. (-0.50 points)

Analysis of lib/src/error_group.dart reported 1 hint:

line 138 col 7: DO use curly braces for all flow control structures.

Maintenance suggestions

Package is getting outdated. (-5.21 points)

The package was last published 54 weeks ago.

Dependencies

Package Constraint Resolved Available
Direct dependencies
Dart SDK >=2.0.0 <3.0.0
args ^1.4.1 1.6.0
async ^2.0.0 2.4.1
crypto >=1.0.0 <3.0.0 2.1.4
http ^0.12.0 0.12.0+4
http_multi_server >=1.0.0 <3.0.0 2.2.0
meta ^1.1.0 1.1.8
path ^1.2.0 1.6.4
pool ^1.0.0 1.4.0
pub_semver ^1.4.0 1.4.4
resource ^2.1.5 2.1.6
source_span ^1.4.0 1.7.0
stack_trace ^1.0.0 1.9.3
yaml ^2.0.0 2.2.0
Transitive dependencies
charcode 1.1.3
collection 1.14.12
convert 2.1.1
http_parser 3.1.4
pedantic 1.9.0
string_scanner 1.0.5
term_glyph 1.1.0
typed_data 1.1.6
Dev dependencies
test ^1.0.0