1. 03 Jul, 2018 1 commit
    • Danny Tuppeny's avatar
      Upgrade node on travis (#18994) · 6172e23c
      Danny Tuppeny authored
      * Upgrade to current LTS version of Node
      
      The version of NPM with Node 6 is over a year old and frequently hangs trying to install Firebase tools.
      
      * Temporarily comment out this condition so the install runs on Travis
      
      * Revert "Temporarily comment out this condition so the install runs on Travis"
      
      This reverts commit 74db9366b4b1b094369388ef50fb26f3b7fd3104.
      
      * Pin to nodejs v8.1
      6172e23c
  2. 16 Mar, 2018 1 commit
  3. 15 Mar, 2018 2 commits
    • Vyacheslav Egorov's avatar
      Upgrade packages to pull in newest petitparser with Dart 2 fixes. (#15558) · d693d427
      Vyacheslav Egorov authored
      * Upgrade packages to pull in newest petitparser with Dart 2 fixes.
      
      * Don't allow Dart 2 failures.
      
      * Address new lints discovered by updated analyzer.
      d693d427
    • Siva's avatar
      Engineroll (#15547) · 8c75dcf1
      Siva authored
      * iupdate engine version to 141176b9004d7b01325629fd45b2ef61b0d00251
      
      * update engine version to f192c59d76c0afe63f2290c3ed76061f00c77cc7
      This rolls dart to version 0175f24b2549732d0010708988fd328440c3f956
      
      * Move dart 2 tests back to optional section to allow debugging of a new
      regression in the petitParser package.
      
      * Update
      8c75dcf1
  4. 14 Mar, 2018 1 commit
  5. 01 Mar, 2018 1 commit
    • Alexander Aprelev's avatar
      Run flutter tests in preview-dart-2 mode on travis flutter builds. (#14728) · d3797628
      Alexander Aprelev authored
      * Run flutter tests in preview-dart-2 mode on travis flutter builds.
      
      * Run dart2 tests on osx. Run dart tests in dart2.
      
      * Fix name camelCase
      
      * Default options to empty array, rather than null
      
      * Troubleshoot failures
      
      * More logging
      
      * Troubleshoot: run single test
      
      * Troubleshoot: run 15 tests
      
      * Troubleshoot: run 15 tests with fix
      
      * Try limit concurrency to 1
      
      * Limit concurrency for preview-dart-2 tests to 4
      
      * Move dart2 tests to allow_failures section
      
      * Reinstate tests_dart_2 shard
      
      * Raise concurrency to 8
      
      * Reuse compiler across multiple test runs
      
      * Allow to switch entry points when recompiling.
      
      Actually use single compiler to incrementally recompile all tests executed by 'flutter test'.
      
      * Remove leftover commented code
      
      * Fix comment
      
      * Lints
      d3797628
  6. 21 Feb, 2018 1 commit
  7. 05 Feb, 2018 1 commit
  8. 18 Jan, 2018 1 commit
    • Ian Hickson's avatar
      New release process (#14061) · 9e42e4b8
      Ian Hickson authored
      Generate the "version" file from git tags.
      Remove the old VERSION file and mentions of versions in pubspec.yaml files.
      Replace the old update_versions.dart script with a new roll_dev.dart script.
      Update "flutter channel".
      Update "flutter upgrade", including making it transition from alpha to dev.
      Update "flutter --version" and "flutter doctor".
      9e42e4b8
  9. 16 Nov, 2017 1 commit
  10. 07 Sep, 2017 1 commit
  11. 07 Aug, 2017 1 commit
  12. 04 Aug, 2017 1 commit
    • Jason Simmons's avatar
      Disable the coverage shard in Travis (#11512) · 7df854ad
      Jason Simmons authored
      In a Travis environment, the test package is exiting the process after
      completing the tests.
      See dart-lang/test@d1057c4
      
      The flutter test command calls the test package's main() and then expects to
      do other work afterward.  The exit prevents flutter test from writing the
      new coverage results, causing the coveralls tool to run against an old
      lcov.info file.
      7df854ad
  13. 03 Aug, 2017 2 commits
  14. 10 Jul, 2017 1 commit
  15. 07 Jul, 2017 1 commit
  16. 27 Jun, 2017 4 commits
  17. 23 Jun, 2017 1 commit
  18. 16 Jun, 2017 1 commit
  19. 24 Apr, 2017 1 commit
  20. 09 Mar, 2017 1 commit
  21. 17 Feb, 2017 1 commit
  22. 10 Feb, 2017 1 commit
  23. 08 Feb, 2017 1 commit
  24. 15 Dec, 2016 1 commit
  25. 13 Dec, 2016 1 commit
  26. 22 Nov, 2016 1 commit
  27. 12 Jul, 2016 1 commit
    • Seth Ladd's avatar
      Firebase hosting for docs (#4871) · 1ac08b26
      Seth Ladd authored
      * configs for firebase hosting
      
      * use the implicit FIREBASE_TOKEN
      
      * don't print every command (lowers the chance of printing secret env vars, and for realz only deploy when merging into master
      1ac08b26
  28. 08 Jul, 2016 2 commits
  29. 22 Jun, 2016 1 commit
  30. 18 May, 2016 1 commit
    • Ian Hickson's avatar
      Try to simplify our bot setup. (#3986) · 942ccc5c
      Ian Hickson authored
      This moves all the bot-related files to `dev/bots`, hiding it from our
      home page in github. Also, simplifies the travis setup, though that
      doesn't do any difference to the performance sadly.
      942ccc5c
  31. 15 Dec, 2015 1 commit
  32. 14 Dec, 2015 1 commit
  33. 21 Nov, 2015 1 commit
  34. 12 Nov, 2015 1 commit
    • Hixie's avatar
      Make the analyzer actually work. · 8ab229f8
      Hixie authored
      Turns out that ignoring all error lines that match the empty string is a
      poor way to go.
      
      Also, we have to update all the example packages now too, since we
      analyze them. So just have travis use our update script.
      
      Also, remove flutter_tools' old travis stuff. It's now part of a bigger
      repo.
      
      Also, make travis use the dev Dart SDK, since we need the new analyzer.
      Stable is way too out of date, e.g. it still complains about libraries
      not having names and mixins using 'super', and the strong mode hints are
      even more aggressive than on dev.
      8ab229f8