...
- Decide on approach to take around resource heavy parts of the process:
- Can we use an external ledger to eliminate the need for spinning up a ledger for Indy SDK tests?
- Can we use version controlled docker images with pre-loaded dependencies to reduce build times?
- What platforms will we prioritize?
- Can we eliminate some of the artifacts - e.g. indy-crypto?
- Convert from Jenkins to
either (TBD)GHAor AZP. Decision: Per Brett Loganit's super easy to switch between the two (just key names are different) and admin overhead is less with GHA.- This is the big effort - lots of detail and tasking to be done.
- Given the scope of the indy-sdk CI/CD scripts - does anyone know the ballpark effort of this? Best approach to sharing (or not) the work?
- Iteratively complete the tasks
- This is the big effort - lots of detail and tasking to be done.
- Evaluate the best platform (GHA or AZP or similar) for different pipelines to use long term – GHA or AZPterm based on their requirements.
- Tune the scripts to the selected platform
...