Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: cocoapod cache issue #8306

Merged
merged 7 commits into from
Jan 19, 2024
Merged

fix: cocoapod cache issue #8306

merged 7 commits into from
Jan 19, 2024

Conversation

vinistevam
Copy link
Contributor

@vinistevam vinistevam commented Jan 17, 2024

Description

This PR aims to fix an issue when run ios build when a dependency is updated. After analysing the latest cases reported facing issues with ios build I realised that cocoapod restore was overwriting the cocoa pod install in the yarn setup step. So, I moved the restore cocoa pod cache on top of the yarn setup step to take advantage of the cache and properly update the new dependencies.

Pipeline error: https://app.bitrise.io/build/8ae57475-c72a-41ce-96f2-d3b6768b9d16
Error:

PhaseScriptExecution [CP]\ Check\ Pods\ Manifest.lock /Users/vagrant/git/ios/build/Build/Intermediates.noindex/MetaMask.build/Debug-iphonesimulator/MetaMask.build/Script-99E9B9D94E374E1799EFBA99.sh (in target 'MetaMask' from project 'MetaMask')
(1 failure)
error Command failed with exit code 65.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Related issues

Fixes: https://github.com/MetaMask/mobile-planning/issues/1487

Manual testing steps

  1. Update a dependency
  2. Run smoke pipeline
  3. Install cocoapod should run and update the cache

Screenshots/Recordings

Before

Pipeline updating cocoa pod:
https://app.bitrise.io/build/8ae57475-c72a-41ce-96f2-d3b6768b9d16

After

Pipeline updating cocoa pod adding back the cocopod install step:
https://app.bitrise.io/build/8631a2cf-89f7-4025-964f-4c8bfeb4e28c

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • I've clearly explained what problem this PR is solving and how it is solved.
  • I've linked related issues
  • I've included manual testing steps
  • I've included screenshots/recordings if applicable
  • I’ve included tests if applicable
  • I’ve documented my code using JSDoc format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
  • I’ve properly set the pull request status:
    • In case it's not yet "ready for review", I've set it to "draft".
    • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@vinistevam vinistevam added the team-confirmations-system DEPRECATED: please use "team-confirmations" label instead label Jan 17, 2024
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@codecov-commenter
Copy link

codecov-commenter commented Jan 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c6892d1) 40.20% compared to head (8a842c4) 40.20%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8306   +/-   ##
=======================================
  Coverage   40.20%   40.20%           
=======================================
  Files        1235     1235           
  Lines       29926    29926           
  Branches     2872     2872           
=======================================
  Hits        12033    12033           
  Misses      17200    17200           
  Partials      693      693           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@vinistevam vinistevam added the No QA Needed/E2E Only Apply this label when your PR does not need any QA effort. label Jan 17, 2024
@vinistevam vinistevam marked this pull request as ready for review January 17, 2024 10:35
@vinistevam vinistevam requested a review from a team as a code owner January 17, 2024 10:35
@vinistevam
Copy link
Contributor Author

Copy link
Contributor

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f0516007-124a-4beb-ba40-c8305c669c45
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

OGPoyraz
OGPoyraz previously approved these changes Jan 17, 2024
@vinistevam vinistevam changed the title Fix: cocoapod cache issue fix: cocoapod cache issue Jan 17, 2024
bitrise.yml Outdated Show resolved Hide resolved
Copy link
Contributor

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7264e209-ab57-41db-bf18-9d4b7f541d41
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

Copy link
Contributor

@sethkfman sethkfman left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

sonarcloud bot commented Jan 19, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@vinistevam vinistevam merged commit c2ae63c into main Jan 19, 2024
26 checks passed
@vinistevam vinistevam deleted the fix/pod-cache-issue branch January 19, 2024 06:56
@github-actions github-actions bot locked and limited conversation to collaborators Jan 19, 2024
@metamaskbot metamaskbot added the release-7.16.0 Issue or pull request that will be included in release 7.16.0 label Jan 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
No QA Needed/E2E Only Apply this label when your PR does not need any QA effort. release-7.16.0 Issue or pull request that will be included in release 7.16.0 team-confirmations-system DEPRECATED: please use "team-confirmations" label instead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants