Welcome to the Indy CI/CD Page
This section of the Indy documentation contains and links to information on the CI/CD processes being used with Indy.
Indy currently uses Jenkins-based CI/CD pipelines for indy-node, indy-plenum and indy-sdk. There is an active project using this as a home page to convert the existing indy-node and indy-plenum pipelines to use GitHub Actions. As the project progresses, this page will be the index for information on the CI/CD practices that are put in place.
Useful Links
- Previous plan for migrating Indy pipelines – Sovrin resource migration
- Current automated, semi-automated and manual testing being done on releases of Indy and Sovrin Token in preparation for releases and upgrades to Sovrin – https://github.com/sovrin-foundation/sovrin/blob/master/docs/acceptance.md
- The processes should be split into Indy and Sovrin related processes.
Plan
- GitHub Actions for indy-plenum CI
- GitHub Actions for indy-node CI
- For Sovrin upgrades: GitHub Actions for sovrin-token CI
- Identify artifacts and versioning scheme for indy-plenum
- Identify artifacts and versioning scheme for indy-node
- For Sovrin: Identify artifacts and versioning scheme for sovrin-token
- Simplify branching model for indy-plenum
- Simplify branching model for indy-node
- For Sovrin: Simplify branching model for sovrin-token
- GitHub Actions for indy-plenum CD
- GitHub Actions for indy-node CD
- For Sovrin: GitHub Actions for sovrin-token CD
Easy, eh?