Automic VaultAutomic Vault

brew

Installer bluepill avec Homebrew, winget

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de bluepill pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install bluepill

local Homebrew formula metadata

Windows

Windows Package Managervérifié · 92%
winget install --id Ukhirani.Bp -e

Windows Package Manager source index · Ukhirani.Bp · Source: cdn.winget.microsoft.com

aperçu

Résumé du paquet

Testing tool for iOS that runs UI tests using multiple simulators

Commandes et alias

  • bluepill
  • bp

historique

Historique du projet et usages

Bluepill is an iOS test runner created at LinkedIn to run large XCTest and UI-test suites across multiple simulators on one Mac. It became a recognizable package for iOS CI teams because it attacked the slow, flaky simulator-test problem before Apple's own parallel-test story was mature.

Historique du projet

LinkedIn open-sourced Bluepill in January 2017 after building it to run its large iOS test suite in a reasonable amount of time. The README describes its core features: parallel simulator execution, automatic test grouping, headless mode, junit reports, retry behavior, and simulator crash or hang recovery.

The project was originally published under LinkedIn's GitHub organization and later lives under MobileNativeFoundation. Its tags show a long 5.x release line, and the README tracks supported Xcode versions with branches for older Xcode releases.

Historique d'adoption

Bluepill found adoption among iOS teams that needed faster CI feedback without rewriting tests. The README explicitly documents Homebrew installation, release binaries, Fastlane plugin integrations, and a Bitrise build/test step, showing that usage spread through common mobile CI packaging channels.

The surrounding ecosystem included Redpill and other Fastlane plugins, plus Bitrise support, which let teams wire Bluepill into existing build pipelines rather than treating it as a standalone experiment.

Modes d'utilisation

A typical workflow builds an app and test bundle with xcodebuild build-for-testing, then invokes bluepill with the generated .xctestrun file and an output directory. The tool can also read a JSON configuration file via -c/--config, but the README documents this as a user-supplied file rather than a fixed config path.

Operationally, Bluepill matters because it packs tests into simulator groups, controls retry behavior, collects junit output, and can run headless to reduce resource use on CI machines.

Pourquoi les passionnés de paquets s'y intéressent

Bluepill is significant because it packages a hard local-platform problem: reproducible iOS simulator parallelism. For package nerds, it is a case study in a CLI wrapping Xcode artifacts, Simulator behavior, junit reporting, and CI integration into something installable with Homebrew.

It also marks a particular era of iOS infrastructure, when teams combined xctool, FBSimulatorControl ideas, Fastlane plugins, and custom runners to make Apple-platform testing scale in CI.

Chronologie

  • 2017: LinkedIn open-sourced Bluepill and published early v0.x tags.
  • 2017: README credits inspiration from parallel_ios_tests, Facebook xctool, and FBSimulatorControl.
  • 2017-2018: Fastlane and Bitrise integrations appeared around the project ecosystem.
  • 2024: Official repository metadata and tags show continued releases through the 5.x line, including Xcode 15.1-era work.

Related projects

  • parallel_ios_tests inspired the project.
  • Facebook xctool and FBSimulatorControl are credited by the README as inspirations.
  • Fastlane plugins such as Redpill, fastlane-plugin-bluepill, Bluepillar, and XBluepill integrated Bluepill into mobile release workflows.
  • Bitrise's Bluepill Build/Test for iOS step connected it to hosted CI.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 8 plateformes.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

exécutables

Exécutables installés

CommandeTypeExpositionNote
bluepillcliexécutable global
bpcliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire5.13.0
gestionnaire mis à jour
données localesOK
amontnot checked
dernière version détectéenon détecté

https://github.com/MobileNativeFoundation/bluepill

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:bluepill
Version5.13.0
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/bluepill
Page d'accueilhttps://github.com/MobileNativeFoundation/bluepill
Dépôthttps://github.com/MobileNativeFoundation/bluepill
Docs amonthttps://github.com/MobileNativeFoundation/bluepill#readme
LicenceBSD-2-Clause
Archive sourcehttps://github.com/MobileNativeFoundation/bluepill.git
Bouteilledisponible (sur arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namebluepill
Version Scheme0
Revision0
Head VersionHEAD
Requirements
  • macos
  • xcode
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

winget92%

Ukhirani.Bp

winget install --id Ukhirani.Bp -e
  • installed executable or alias match
  • Correspondance par : Bp
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Ukhirani.Bp from https://cdn.winget.microsoft.com/cache/source.msix

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment