Skip to content

big_red_button.py should run the same tests as travis #244

Closed

Description

@FlutterIssues

Issue by Hixie
Thursday Oct 29, 2015 at 23:42 GMT
Originally opened as https://github.com/flutter/engine/issues/1880


Somehow we should verify that the release we're about to make will be analyzer-clean and pass the tests. This is complicated by the fact that during the release your tree is in a state where 'pub' won't be happy, of course.

Activity

  1. FlutterIssues commented on Nov 9, 2015

    @FlutterIssues
    Author

    Comment by abarth
    Friday Oct 30, 2015 at 16:41 GMT


    I discussed this with @sethladd . One idea is to be able to push a "beta" or "dev" version of the packages to pub that won't be visible to the public. Then we could test them from pub and once they pass the test, we could flip the bit on the server and make them the production versions of the package.

  2. abarth commented on Dec 5, 2015

    @abarth
    Contributor

    We now release using git hashes. We should check Travis before publishing a given git hash.

  3. github-actions commented on Sep 7, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  4. locked as resolved and limited conversation to collaborators on Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    c: contributor-productivityTeam-specific productivity, code health, technical debt.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions