vela-services

Manage service containers in Vela CI/CD pipelines for integration testing.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/ryanmr/vela-skills --skill vela-services
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vela-services
Source: https://github.com/ryanmr/vela-skills/tree/main/.agents/skills/vela-services
Command: npx skills add https://github.com/ryanmr/vela-skills --skill vela-services

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables the seamless integration of service containers like databases and caches directly into Vela CI/CD pipelines, simplifying the setup for integration testing.

Core Features & Use Cases

  • Service Container Orchestration: Define and run dependent services (e.g., PostgreSQL, Redis, Elasticsearch) alongside your build steps.
  • Network Accessibility: Services are automatically discoverable by their defined name within the pipeline's network.
  • Use Case: Integrate a PostgreSQL database as a service to run your application's integration tests against a real database instance within the CI environment.

Quick Start

Use the vela-services skill to define a postgres service container named 'db' using the 'postgres:16-alpine' image.

Frequently Asked Questions about vela-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run service containers for integration tests in a CI/CD pipeline?▼

To run service containers for integration tests, you can orchestrate dependent services like databases directly within your CI/CD pipeline. This allows build steps to access and test against real instances automatically.

How do I add a PostgreSQL database to my integration testing environment?▼

You can add a PostgreSQL database to your integration testing environment by defining it as a service container. Specify a custom image like postgres:16-alpine and configure the necessary environment variables.

How are service containers discovered for networking in CI/CD integration tests?▼

Service containers are automatically discoverable by their defined name within the pipeline's network. This allows your build steps to connect to the services seamlessly during integration testing.

Do I need to handle service readiness checks before running dependent pipeline steps?▼

Yes, you need to explicitly handle service readiness checks. Ensuring stability before dependent steps execute prevents integration test failures caused by services that are still initializing.

Can I run multiple service containers with custom environment variables in my pipeline?▼

Yes, you can run multiple service containers with custom environment variables. The orchestration supports defining multiple services with custom images and networking configurations simultaneously.