RabbitMQ: 3. Pick the instance size

This documentation is part of the GitHub Actions & GitLab CI guide. View the full guide here: Spin up a real RabbitMQ service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically.

The examples below use the entry-level instance 200 for RabbitMQ by default. This is a solid choice for most workloads, but you are welcome to adjust it as needed. To view all available instance types for RabbitMQ, you can run:

# The NAME column shows the value to pass to --instance
stackhero instances-store-list --service-store=rabbitmq

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Spin up a real RabbitMQ service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically
  2. 1. Create an access token and store it as a CI secret
  3. 2. The lifecycle script
  4. 4. GitHub Actions
  5. 5. GitLab CI

Other articles for RabbitMQ

  1. Introduction
    Introduction to Stackhero for RabbitMQ
  2. Getting started
    How to use Stackhero for RabbitMQ
  3. Automate with the CLI
    Start RabbitMQ, retrieve its credentials, and change its configuration programmatically with the Stackhero CLI