Skip to content

ci-cd.md

Latest commit

 

History

History
39 lines (29 loc) · 1.35 KB

ci-cd.md

File metadata and controls

39 lines (29 loc) · 1.35 KB
Raw

CI/CD Guide

This document describes how automated testnet deployment works and how to set up the deployer secret.

Testnet Deployment Workflow

The workflow at .github/workflows/deploy-testnet.yml deploys all contracts to Stellar testnet on each push to main, then updates README contract IDs.

What it does

  • Builds optimized WASM for all contracts.
  • Deploys to Stellar testnet using a dedicated deployer account.
  • Updates the README testnet contract IDs table.
  • Pushes README updates back to main with a [skip ci] commit message.
  • Exposes a deployment summary as a workflow output.

Required Secrets

Create a deployer keypair and store the secret key as a GitHub Actions secret.

  1. Create a testnet deployer key: 
    stellar keys generate --global testnet-deployer
stellar keys address testnet-deployer
  2. Fund the account: 
    stellar network fund testnet-deployer --network testnet
  3. Add the secret to GitHub:
    • Settings -> Secrets and variables -> Actions -> New repository secret
    • Name: STELLAR_TESTNET_DEPLOYER_SECRET
    • Value: the secret key from stellar keys show testnet-deployer

Notes

  • Use a dedicated deployer account for automation only.
  • Rotate the deployer key periodically and update the secret.
  • If the workflow fails to deploy, check Stellar testnet status and rerun the job.