...
- 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?
- Notably, we'll do one first (Linux, likely), and then likely MacOS, followed by Windows. The community will decide what to do (or not do) after that.
- 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 based on their the pipeline requirements.
- Tune the scripts to the selected platform
Tentative Plan for indy-sdk migration:
- Migrate CI Linux
- Evaluate/possibly refactor ledger interactions (depends on effort of changes per test case)
- Evaluate/possible refactor docker images approach
- Migrate CD Linux
- Migrate Linux artifact publishing
- Migrate MacOS CI
- Migrate MacOS CD
- Migrate Windows CI
- Migrate Windows CD
Ideally, one person does the first four steps, supported through questions to others, and with reviews with a group at the end of each step. After that, we can expand out the work to more people, and we can apply the same approach to the other repos.
Hyperledger Paid For Resources
...