chore: timeout build android apk for e2e 40 minutes

[tommasini]

Description

timeout build android apk for e2e 40 minutes

Reference of taking only 19 minutes https://github.com/MetaMask/metamask-mobile/actions/runs/19541397562/job/55948548693

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• 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.

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.

---

Note

Adds timeout-minutes: 40 to the build-android-apks job in .github/workflows/build-android-e2e.yml.

^{Written by Cursor Bugbot for commit c66917a. This will update automatically on new commits. Configure here.}

[github-actions]

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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

This PR contains a single change to .github/workflows/build-android-e2e.yml that adds a timeout-minutes: 40 configuration to the Android APK build job.

Change Analysis:

• The modification only adds a timeout parameter to prevent the job from running indefinitely
• No application code changes
• No changes to the build process, dependencies, or environment variables
• No modifications to how APKs are built or what is included in them
• No changes to test execution logic

Why no E2E tests are needed:

1. Pure Infrastructure Change: This is solely a CI/CD workflow configuration that controls job execution limits
2. No Functional Impact: The timeout setting does not affect the resulting APK artifacts, application behavior, or any features
3. Standard CI Practice: Adding timeouts is a defensive measure to prevent hanging jobs; it's not related to application functionality
4. Build Output Unchanged: The APKs built with or without this timeout will be functionally identical

Verification Approach:
The appropriate verification for this change is:

• Observing that the workflow completes successfully within the timeout window
• Confirming the job doesn't run indefinitely if issues occur
• No E2E testing needed as no application functionality is affected

Risk Assessment:

• Very low risk - cannot affect application behavior or user experience
• High confidence in this assessment - the change is straightforward and isolated to CI configuration

View GitHub Actions results

[Gudahtt]

LGTM!

We should add timeouts to to all jobs, but this is a good start

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud