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

[CI]: Update Iroha 1 branch workflow #185

Merged
merged 2 commits into from Apr 23, 2024

Conversation

nxsaken
Copy link
Contributor

@nxsaken nxsaken commented Apr 23, 2024

Fix branch name, rename workflow file

Signed-off-by: Nurzhan Sakén <nurzhan.sakenov@gmail.com>
Comment on lines 3 to 7
push:
branches:
- iroha1-main
tags:
- '*'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
push:
branches:
- iroha1-main
tags:
- '*'
push:
tags:
- 'v1*'

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should differentiate between publishing a release and merging into main

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

releases should only be built from tags

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The scope of this PR is to fix the branch name and the workflow file name (to avoid confusion), the rest I left as it was

Copy link

@mversic mversic Apr 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@mversic
Copy link

mversic commented Apr 23, 2024

should you merge this into main or iroha1-main?

@nxsaken
Copy link
Contributor Author

nxsaken commented Apr 23, 2024

It's unclear to me at this point (not a GitHub CI expert), seems like it doesn't matter as long as the target branches are specified in the workflow files.

@mversic
Copy link

mversic commented Apr 23, 2024

It's unclear to me at this point (not a GitHub CI expert), seems like it doesn't matter as long as the target branches are specified in the workflow files.

then let's merge it into iroha1-main

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you renamed the file, shouldn't you delete the old file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's strange, renaming the file should have deleted the old version.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you didn't commit the deleted file

Signed-off-by: Nurzhan Sakén <nurzhan.sakenov@gmail.com>
@nxsaken nxsaken merged commit cc7461c into hyperledger:main Apr 23, 2024
1 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants