github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 03:33:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[PR #6181] [PM-28504] Add testharness build workflow with dynamic versioning #6383

New Issue
Open
opened 2025-11-27 00:23:01 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-27 00:23:01 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/bitwarden/android/pull/6181

State: open
Merged: No

🎟️ Tracking

PM-28504

📔 Objective

Add GitHub Actions workflow for building the testharness module via manual workflow dispatch.

This PR introduces .github/workflows/build-testharness.yml to enable on-demand testharness APK builds through GitHub Actions, following the established patterns from the app and authenticator build workflows.

Key changes:

  • New workflow: build-testharness.yml with workflow_dispatch trigger for manual builds
  • Dynamic versioning: Integrates with _version.yml reusable workflow (codename: "bwth", base version: 0)
  • Fastlane integration: Uses setBuildVersionInfo for version management consistency
  • Build output: Generates com.bitwarden.testharness.dev-debug.apk with SHA256 checksum
  • Version configuration: Updated testharness/build.gradle.kts to read version from libs.versions.toml instead of hardcoded values

The workflow enables teams to build and distribute testharness artifacts for credential provider testing and validation without requiring local development environment setup.

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes
**Original Pull Request:** https://github.com/bitwarden/android/pull/6181 **State:** open **Merged:** No --- ## 🎟️ Tracking PM-28504 ## 📔 Objective Add GitHub Actions workflow for building the testharness module via manual workflow dispatch. This PR introduces `.github/workflows/build-testharness.yml` to enable on-demand testharness APK builds through GitHub Actions, following the established patterns from the app and authenticator build workflows. **Key changes:** - **New workflow**: `build-testharness.yml` with workflow_dispatch trigger for manual builds - **Dynamic versioning**: Integrates with `_version.yml` reusable workflow (codename: "bwth", base version: 0) - **Fastlane integration**: Uses `setBuildVersionInfo` for version management consistency - **Build output**: Generates `com.bitwarden.testharness.dev-debug.apk` with SHA256 checksum - **Version configuration**: Updated `testharness/build.gradle.kts` to read version from `libs.versions.toml` instead of hardcoded values The workflow enables teams to build and distribute testharness artifacts for credential provider testing and validation without requiring local development environment setup. ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes
GiteaMirror added the pull-request label 2025-11-27 00:23:01 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#6383
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?