Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

What we have available (are paying for)

from this list, there are some repos to migrate

Jenkins:

Nexus:

  • rpm publishing

Requirements (from this presentation slide from Evernym)

  • Linux, Windows, macOS platforms support.
  • Triggering builds from GitHub PRs sent from fork.
  • Ability to run our integration tests with IndyPool created as docker network on the same machine (maybe there are another solution-related ways)
  • Hardware acceleration for Android’s routines (nice to have).
  • Ability to passing artifacts through CI/CD jobs/steps (to avoid rebuilding artifacts).
  • Run jobs in parallel.
  • Ease of scale (ability to insert new runner machine).

Debian Publishing - repo.sovrin.org

repo.sovrin.org provides debian packages that are used by the Sovrin Stewards to install Indy Node and a Maven interface for developers.  The former use will need to shift to whatever Steward organization forms as a fallout of the Sovrin Foundation transition. The latter us can be transitioned to Hyperledger resources, with a transition notification to the developer community.

  • Stephen Curran Let the MainNet transition team (headed by Riley Hughes) that this is an issue that will need to be addressed by that group.

Background Information

CI/CD Platform Evaluation:

  • 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.

Hyperledger Fabric Experience - from Brett Logan (Deactivated)

Hyperledger Fabric Experience - Azure Pipelines vs GitHub Actions

Lower priority:

Travis:

  • aries-framework-dotnet

Circle-CI:

  • aries-cloudagent-python
  • aries-rfcs
  • indy-hipe
  • No labels