This project is mirrored from https://github.com/flutter/flutter.git.
Pull mirroring updated .
- Feb 22, 2018
-
-
xster authored
-
- Feb 06, 2018
-
- Jan 18, 2018
-
-
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".
-
- Nov 17, 2017
-
-
Greg Spencer authored
-
- Sep 08, 2017
-
-
Michael Goderbauer authored
-
- Aug 08, 2017
-
-
Ian Hickson authored
I forgot to do this when I updated our test package.
-
- Aug 04, 2017
-
-
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.
-
Jacob Richman authored
This reverts commit 0cfd3dec239faf3c13ce759df15ddab226545e8c.
-
Jacob Richman authored
-
- Jul 11, 2017
-
-
Todd Volkert authored
Fixes #7894
-
- Jul 08, 2017
-
-
- Jun 28, 2017
-
-
Todd Volkert authored
This reverts commit b800654a.
-
Todd Volkert authored
This time, do so in Travis' sudo-enabled environment, which is said to be less prone to networking issues. It also means we'll run in an env with 7.5GB of RAM instead of 4GB or RAM (at the cost of about 45 seconds of extra boot-up time). https://github.com/flutter/flutter/issues/10940
-
Ian Hickson authored
This reverts commit aa904a58.
-
Todd Volkert authored
Fixes #10940
-
- Jun 24, 2017
-
-
- Jun 16, 2017
-
-
Todd Volkert authored
-
- Apr 24, 2017
-
-
Michael Thomsen authored
* Upgrade node version * Upgrade node version, but no further than 6 which is in LTS
-
- Mar 10, 2017
-
-
Jason Simmons authored
-
- Feb 17, 2017
-
-
Adam Barth authored
-
- Feb 11, 2017
-
-
Michael Goderbauer authored
This used to be the logic before I made the tests portable.
-
- Feb 09, 2017
-
-
Michael Goderbauer authored
-
- Dec 16, 2016
-
-
Ian Hickson authored
-
- Dec 14, 2016
-
-
Chinmay Garde authored
-
- Nov 23, 2016
-
-
Chinmay Garde authored
-
- Jul 13, 2016
-
-
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
-
- Jul 09, 2016
-
-
Adam Barth authored
-
Adam Barth authored
-
- Jun 23, 2016
-
-
Adam Barth authored
This patch causes us to upload a coverage report to coveralls.io.
-
- May 19, 2016
-
-
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.
-
- Dec 15, 2015
-
-
Eric Seidel authored
@abarth
-
Eric Seidel authored
Makes it more obvious where we are spending our time on Travis. Also added travis caching for the global pub cache to speed this up! Modeled what dartdoc does: https://github.com/dart-lang/dartdoc/blob/master/.travis.yml#L13 @Hixie
-
- Nov 22, 2015
-
-
Adam Barth authored
Hopefully this will make Travis green.
-
- Nov 13, 2015
-
-
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.
-
- Nov 07, 2015
-
-
Adam Barth authored
-
- Nov 03, 2015
-
-
Adam Barth authored
-