cesarferreira/dryrun
Dryrun
Dryrun is a command-line tool designed to automate the end-to-end lifecycle of Android projects, including cloning, building, and deploying source code from remote repositories to connected devices. It functions as a build system wrapper and device deployment tool that programmatically invokes native Android build tools to compile applications without requiring manual configuration in an integrated development environment.
The project differentiates itself through an ephemeral workspace orchestrator that creates and destroys temporary file system environments to ensure every project execution starts from a clean and isolated state. It also includes a remote repository test runner that fetches source code and executes automated test suites directly from version control.
The tool's capabilities cover version control authentication for accessing both public and private repositories, build configuration management for specifying branches, tags, and flavors, and platform-interface deployment to install artifacts on physical hardware or emulators.
Features
- Ephemeral Workspaces - Orchestrates the creation and destruction of temporary file system environments to ensure isolated and clean builds.
- Project Runners - Clones and builds remote repositories and starts the application on a connected device without manual project imports.
- Android Build Automation - Automates the end-to-end pipeline of cloning, building, and deploying Android projects using ephemeral workspaces.
- Device Deployment - Communicates with connected physical hardware or emulators to install and launch compiled Android application artifacts.
- Project Lifecycle Automators - Provides a command-line interface to coordinate the end-to-end sequence of cloning, building, and deploying Android projects.
- Native Toolchain Orchestrators - Programmatically invokes platform-specific command-line build systems to compile and package Android projects.
- Android Device Deployment Utilities - Automates the installation and execution of compiled Android artifacts on physical hardware or emulators.
- Build Tool Wrappers - Programmatically invokes native Android build tools to compile and package projects without requiring manual IDE setup.
- Build Lifecycle Managers - Coordinates the sequence of downloading, building, testing, and cleaning up project files to streamline remote code evaluation.
- Automated Test Execution - Automates the execution of Android test suites on connected devices via a command-line interface.
- Test Suite Runners - Provides a utility to manage and execute Android test suites retrieved directly from remote version control.
- Build Configuration Mappings - Translates user-specified branches, tags, and flavors into specific parameters for the native Android build system.
- Library Demo Evaluation - Tests remote Android libraries by automatically cloning and launching demo projects without manual setup.
- Android Prototyping Tools - Quickly downloads and runs remote Android source code to verify functionality without local environment configuration.
- Build Configuration Management - Allows defining custom modules, build flavors, and version tags to target specific project configurations.
- Remote Repository Authentication - Supports secure authentication with remote repositories using standard protocols to fetch source code for builds.
- Private Repository Access - Implements mechanisms to authenticate and retrieve source code from private git repositories.
- Version Control Authentications - Interfaces with repository protocols to securely fetch source code from both public and private remote servers.
- Remote-to-Device Test Runners - Executes automated Android test suites on physical devices or emulators directly from version control URLs.
- Development Tooling - CLI tool for testing online Android libraries.
- Mobile Development - Tests Android libraries directly from the command line.
Star history
How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
