Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split CI configuration #187

Open
nxsaken opened this issue Apr 23, 2024 · 1 comment
Open

Split CI configuration #187

nxsaken opened this issue Apr 23, 2024 · 1 comment
Labels
infrastructure CI/CD, Pipeline

Comments

@nxsaken
Copy link
Contributor

nxsaken commented Apr 23, 2024

ok, but we should split our CI into these workflows:

  1. workflow that runs on every merge to main
  2. workflow that runs on every merge to iroha1-main
  3. workflow that runs on every v1* tag
  4. workflow that runs on every v2* tag

I think these should all be separate CI files, but maybe you can make them into 2 files (one for merge and one for tags) if the corresponding workflows are the same for iroha1 and iroha2

Originally posted by @mversic in #185 (comment)

@mversic
Copy link

mversic commented Apr 23, 2024

  1. should build the iroha2 python sdk and run all tests
  2. should build the iroha1 python sdk and run all tests
  3. should publish iroha1 sdk
  4. should publish iroha2 sdk

@nxsaken nxsaken added the infrastructure CI/CD, Pipeline label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure CI/CD, Pipeline
Projects
None yet
Development

No branches or pull requests

2 participants