Automated pipelines that build, test, and deploy code when changes are pushed. For Solana programs: CI runs `anchor build`, `anchor test`, linting, and security checks. CD automates deployment to devnet/mainnet with multisig approval. GitHub Actions, GitLab CI, and Vercel are common tools. CI/CD catches bugs early and ensures reproducible builds.
Empieza por la explicación más corta y útil antes de profundizar.
Automated pipelines that build, test, and deploy code when changes are pushed. For Solana programs: CI runs `anchor build`, `anchor test`, linting, and security checks. CD automates deployment to devnet/mainnet with multisig approval. GitHub Actions, GitLab CI, and Vercel are common tools. CI/CD catches bugs early and ensures reproducible builds.
Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.
Piensa en esto como un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Serialización, memoria, estructuras de datos y bases de ingeniería.
Convierte el término de vocabulario en algo operacional para producto e ingeniería.
Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.
Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.
CI/CD (Continuous Integration / Deployment) (ci-cd) Categoría: Fundamentos de Programación Definición: Automated pipelines that build, test, and deploy code when changes are pushed. For Solana programs: CI runs `anchor build`, `anchor test`, linting, and security checks. CD automates deployment to devnet/mainnet with multisig approval. GitHub Actions, GitLab CI, and Vercel are common tools. CI/CD catches bugs early and ensures reproducible builds. Aliases: CI/CD Relacionados: Pruebas (Programas Solana), Solana Verify (solana-verifiable-build)
Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.
Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.
El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.
Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.
The process of validating Solana programs through unit tests, integration tests, and fuzz testing. Common approaches: Rust tests with solana-program-test or LiteSVM (fast, in-process), TypeScript tests with Bankrun or solana-test-validator (end-to-end), and fuzz testing with Trident. Best practice is testing both happy paths and attack vectors (missing signers, wrong owners).
A tool and standard for verifying that deployed on-chain program bytecode matches public source code. `solana-verify build` produces a deterministic build using Docker, and `solana-verify verify-from-repo` checks the deployed binary against a Git repo. Verified programs are listed on the Solana Explorer and OtterSec's verify registry, increasing user trust.
Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
The process of validating Solana programs through unit tests, integration tests, and fuzz testing. Common approaches: Rust tests with solana-program-test or LiteSVM (fast, in-process), TypeScript tests with Bankrun or solana-test-validator (end-to-end), and fuzz testing with Trident. Best practice is testing both happy paths and attack vectors (missing signers, wrong owners).
A tool and standard for verifying that deployed on-chain program bytecode matches public source code. `solana-verify build` produces a deterministic build using Docker, and `solana-verify verify-from-repo` checks the deployed binary against a Git repo. Verified programs are listed on the Solana Explorer and OtterSec's verify registry, increasing user trust.
Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.
A systems programming language emphasizing memory safety, zero-cost abstractions, and concurrency without a garbage collector. Rust uses an ownership model with borrow checking at compile time to prevent data races and null pointer bugs. It is the primary language for Solana program development (via Anchor or native solana-program crate) and the Agave validator client.
A statically typed superset of JavaScript that compiles to plain JavaScript. TypeScript adds type annotations, interfaces, generics, and enums to catch errors at compile time. It is the standard language for Solana client-side development—wallet adapters, dApp frontends, test suites, and SDK interactions (web3.js, Anchor client) are typically written in TypeScript.
The ubiquitous scripting language for web development, running in browsers and Node.js. JavaScript is dynamically typed and event-driven. Most Solana dApp frontends and scripts use JavaScript/TypeScript with libraries like @solana/web3.js. Node.js enables server-side JS for backend services, indexers, and bot development.
A JavaScript runtime built on Chrome's V8 engine that enables server-side JavaScript execution. Node.js uses an event-driven, non-blocking I/O model. In the Solana ecosystem, Node.js is used for: running Anchor tests (Mocha/Jest), backend services, transaction bots, indexers, and CLI tools. npm/yarn/pnpm manage JavaScript package dependencies.