Page History

...

Migration Scope: (from this list)

indy-sdk - CI Script * CD Script
- Most active and slowest build/test process at 5 hours per PR.
indy-node - CI Script * CD Script
indy-plenum - CI Script * CD Script
indy-crypto - CI Script * CD Script
- Question: Ursa is on AZP, so one would think this would be relatively easy to switch?
- Question: On the other hand, can we just eliminate the repo in favour of ursa?
indy-node - CI Script * CD Script
indy-plenum - CI Script * CD Script
indy-sdk - CI Script * CD Script
- Most active and slowest build/test process at 5 hours per PR.

...

This sprint demo reviews Evernym's evaluation of options for CI / CD (tracked in this JIRA issue - login required) where we recommended GitHub Actions based on this presentation summary. Discussed on this Indy Contributors call (with a failed recording).
- Recommendation was GitHub Actions (and Azure Pipelines where necessary/useful).
- Additional recommendation from that was to drop the number of supported platforms, particularly in the mobile area.
Anticipated impacts of moving to GitHub Actions:
- The approach to running a pool for testing will need to be very different from that taken by Jenkins, so the scripts will have to be reworked.
- Indy SDK currently supports a broad range of environments (Ubuntu, RedHat, Windows, OSX, iOS, Android), but we agreed that we can reduce the number of environments and people who miss those artifacts can contribute those build resources.
- The testing pipeline takes a long time because there are a lot of tests–was 3.5 hours per PR with full AWS set of machines, now at 5 hours with reduced AWS machines, and GitHub Actions is likely to be slower.
- This document covers findings about using GitHub actions with some useful links as we begin implementations, with expected positives and only technical negative related to managing a docker repo.
Feel free to test here

...