Try   HackMD

CICD Development Plan

QFI Repository

CI pipeline of QFI with linting and testing will be shipped step by step; considering the current repository status. It is intended to adopt earlier as possible to prevent accumulated errors which are cumbersome to fix it.

Contracts package

CI Flow

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

Current Status

  • Lint fails in Solidity codes
  • Lint fails in Typescript codes
  • Tests fails (due to maci bugs)

Subgraph package

CI Flow

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

Current Status

Step 1. CI with Lint Checking

CI will be functional with restricted scope even before failed tests fixed.

Step 2. CI with Tests Checking

If the current bugs are fixed, CI will also check tests.

Step 3. CI with Package Publishing

Both (1) version tagging to npm and (2) merge event to main branch will trigger publish

Last changed by 
 
mdhackmdkakao
0
133

Read more

The Power of Your Ethcon Korea 2023 Ticket: Fuelling Innovation and Collective Success

What is Ethcon?Ethcon is more than a hackathon. It’s a platform for innovation, fostering a community of creative minds. With a $79 ticket, you get a lot more than just an event pass.

Aug 3, 2023
MACI NPM publish workflow

manual: Bump the version automated: Publish package(s) to NPM Bump the version Maintainer bump the version of sub-package(s). Versioning should follow semver. Method lerna version is handy tool to bump sub-pakcage(s)

Apr 27, 2022
QFI NPM Package Releasing

target packages contracts subgraph Scenario Regular release cycle Create PR; /dev branch into /main branch

Apr 26, 2022
QFI CI/CD pipeline

Contracts package When pull reqeust opened or code is pushed to a specific branch (main, dev) or any tags are pushed, it triggers GitHub Actions. Then GitHub Actions runs three parallel CI jobs to get the test result early as possible. The tests are: Unit test and linting QV test QF test Coverage Every code pushed to main branch trigger to generate code coverage.

Apr 12, 2022
Read more from mdhackmdkakao
Published on HackMD