Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@ricardoamador
Copy link
Contributor

@ricardoamador ricardoamador commented Jun 2, 2022

Description of The Issue Being Addressed

The builder config is fragile when dependencies are not pinned to specific versions. Any upstream changes may cause breakage. We should create a test to validate all .ci.yaml dependencies are pinned. This also requires that we pin specific versions for all dependencies.

Issues Addressed

flutter/flutter#101712

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
  • I listed at least one issue that this PR fixes in the description above.
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt. See testing the engine for instructions on
    writing and running engine tests.
  • I updated/added relevant documentation (doc comments with ///).
  • I signed the CLA.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@CaseyHillers
Copy link
Contributor

Tree is red. Once https://flutter-dashboard.appspot.com/#/build?repo=engine&branch=main goes green, you'll need to rebase this PR with upstream/main.

git fetch --all
git rebase upstream/main

@ricardoamador
Copy link
Contributor Author

Thank you Casey! I will make those changes.

@ricardoamador ricardoamador force-pushed the validate_ci_yaml_deps_pinned branch from efa05df to 77a8aaf Compare June 2, 2022 20:19
Copy link
Contributor

@keyonghan keyonghan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. You can add the waiting for tree to go green label to have the bot auto submit.

@ricardoamador
Copy link
Contributor Author

Oh cool I did not know that. Thanks Keyong!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants