[TB] Integrate with FINOS CICD

[evangk6]

Problem/Concern

One of the later steps of the transition would be to ensure we are making use of the appropriate CICD pipeline provided to us. More information would be required at this time.

Proposed Solution

[aaronreed708]

From Mao:

I used to be a big fan of Travis, but after Idera's acquisition, all our contacts left the company and a series of security issues pushed us to switch to GitHub Actions, which is now our preferred platform; that being said, we do have projects using other tools, like CircleCI and CodeFresh (though they're planning to move to GitHub Actions).

[aaronreed708]

review deploy to Netlify, scans and SDK pushing to NPM.

In previous careers, used Prod branch commits to trigger actions. Any opinions on how to do it now?

Proposal:

• keep main as prod branch
• dev to be current working branch for day to day commits
• merge dev into main to "promote"
  • trigger Netlify deploy in TB repo
    • we should probably publish separately to Netlify for a dev commit
  • trigger NPM publish in SDK repo
  • trigger docker image build and push to DockerHub when this is supported
    • tag Docker image to easily identify what came from prod and what came from dev if we decide to publish images for both

Vote: approved by @smithbk, @brycecurtis, @evangk6, @aaronreed708

[aaronreed708]

Add Netlify deployment to dev branch also. Ensure Docker image publishing also part of GitHub Actions.

[aaronreed708]

@TheJuanAndOnly99 or @maoo, could one of you please update the Netlify for a11y-theme-builder to deploy for both main and dev branches now? Maybe the dev one could be "dev.a11y-theme-builder.finos.org"?

[maoo]

Done! https://dev.a11y-theme-builder.finos.org/

[aaronreed708]

Looks like NPM publishing is complete, the switch to dev branch development is complete and the dev deployment is complete. Just need to finish up #481 and then we can close this issue